TRANSFORM DATA TO XML SCHEMAS

Greetings to all Members,
I write in the forum because my desperation is increasing because of an issue / problem I'm having with DataServices.
On the client where I am, DataServices have installed 4.0 and now I need to do a Real-Time Job. I know that to perform such jobs, you must have an XSD schema and that both input and output must be XML. In my case, my connection is through a DataStore which I returned Oracle tables in a schema. My question is: is there any way we can convert these files oracle tables or XML schemas?
The reason I need to create this job, is because I have to generate through this job that calls a web service to those tables
Thanks in advance for the answers and for help
Marga.

You've closed the context, before evening calling getXML
13 DBMS_XMLGEN.closeContext(Ctx);
14 xml := DBMS_XMLGEN.getXML(Ctx);

Similar Messages

XML generation with SAP data using XML schema - Reg

Hello experts,
My requirement is , SAP( ztable data ) data has to be transferred to third party software folder.Third party using XML so they requires output from SAP in XML format.
For that third party software guys told me that they will give their own XML schema to me.I have to generate XML file with SAP data using their XML schema.
Generating XML file with their Schema should be underlined.
I studied that call transformation statement helps for this.
Even then i don't have clear idea about this topic.
Please brief me about how to use their XML schema to generate XML with my own sap data.
Thanks in advance experts.
Kumar

please try this same program    and see it ....
*& Report z_xit_xml_check
REPORT z_xit_xml_check.
TYPE-POOLS: ixml.
TYPES: BEGIN OF t_xml_line,
          data(256) TYPE x,
        END OF t_xml_line.
DATA: l_ixml            TYPE REF TO if_ixml,
        l_streamfactory   TYPE REF TO if_ixml_stream_factory,
        l_parser          TYPE REF TO if_ixml_parser,
        l_istream         TYPE REF TO if_ixml_istream,
        l_document        TYPE REF TO if_ixml_document,
        l_node            TYPE REF TO if_ixml_node,
        l_xmldata         TYPE string.
DATA: l_elem            TYPE REF TO if_ixml_element,
        l_root_node       TYPE REF TO if_ixml_node,
        l_next_node       TYPE REF TO if_ixml_node,
        l_name            TYPE string,
        l_iterator        TYPE REF TO if_ixml_node_iterator.
DATA: l_xml_table       TYPE TABLE OF t_xml_line,
        l_xml_line        TYPE t_xml_line,
        l_xml_table_size TYPE i.
DATA: l_filename        TYPE string.
PARAMETERS: pa_file TYPE char1024 DEFAULT 'c:temporders_dtd.xml'.
* Validation of XML file: Only DTD included in xml document is supported
PARAMETERS: pa_val TYPE char1 AS CHECKBOX.
START-OF-SELECTION.
*   Creating the main iXML factory
    l_ixml = cl_ixml=>create( ).
*   Creating a stream factory
    l_streamfactory = l_ixml->create_stream_factory( ).
    PERFORM get_xml_table CHANGING l_xml_table_size l_xml_table.
*   wrap the table containing the file into a stream
    l_istream = l_streamfactory->create_istream_itable( table = l_xml_table
                                                    size = l_xml_table_size ).
*   Creating a document
    l_document = l_ixml->create_document( ).
*   Create a Parser
    l_parser = l_ixml->create_parser( stream_factory = l_streamfactory
                                      istream        = l_istream
                                      document       = l_document ).
*   Validate a document
    IF pa_val EQ 'X'.
      l_parser->set_validating( mode = if_ixml_parser=>co_validate ).
    ENDIF.
*   Parse the stream
    IF l_parser->parse( ) NE 0.
      IF l_parser->num_errors( ) NE 0.
        DATA: parseerror TYPE REF TO if_ixml_parse_error,
              str        TYPE string,
              i          TYPE i,
              count      TYPE i,
              index      TYPE i.
        count = l_parser->num_errors( ).
        WRITE: count, ' parse errors have occured:'.
        index = 0.
        WHILE index < count.
          parseerror = l_parser->get_error( index = index ).
          i = parseerror->get_line( ).
          WRITE: 'line: ', i.
          i = parseerror->get_column( ).
          WRITE: 'column: ', i.
          str = parseerror->get_reason( ).
          WRITE: str.
          index = index + 1.
        ENDWHILE.
      ENDIF.
    ENDIF.
*   Process the document
    IF l_parser->is_dom_generating( ) EQ 'X'.
      PERFORM process_dom USING l_document.
    ENDIF.
*&      Form get_xml_table
FORM get_xml_table CHANGING l_xml_table_size TYPE i
                              l_xml_table      TYPE STANDARD TABLE.
*   Local variable declaration
    DATA: l_len      TYPE i,
          l_len2     TYPE i,
          l_tab      TYPE tsfixml,
          l_content TYPE string,
          l_str1     TYPE string,
          c_conv     TYPE REF TO cl_abap_conv_in_ce,
          l_itab     TYPE TABLE OF string.
    l_filename = pa_file.
*   upload a file from the client's workstation
    CALL METHOD cl_gui_frontend_services=>gui_upload
      EXPORTING
        filename   = l_filename
        filetype   = 'BIN'
      IMPORTING
        filelength = l_xml_table_size
      CHANGING
        data_tab   = l_xml_table
      EXCEPTIONS
        OTHERS     = 19.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
*   Writing the XML document to the screen
    CLEAR l_str1.
    LOOP AT l_xml_table INTO l_xml_line.
      c_conv = cl_abap_conv_in_ce=>create( input = l_xml_line-data replacement = space ).
      c_conv->read( IMPORTING data = l_content len = l_len ).
      CONCATENATE l_str1 l_content INTO l_str1.
    ENDLOOP.
    l_str1 = l_str1+0(l_xml_table_size).
    SPLIT l_str1 AT cl_abap_char_utilities=>cr_lf INTO TABLE l_itab.
    WRITE: /.
    WRITE: /' XML File'.
    WRITE: /.
    LOOP AT l_itab INTO l_str1.
      REPLACE ALL OCCURRENCES OF cl_abap_char_utilities=>horizontal_tab IN
        l_str1 WITH space.
      WRITE: / l_str1.
    ENDLOOP.
    WRITE: /.
ENDFORM.                    "get_xml_table
*&      Form process_dom
FORM process_dom USING document TYPE REF TO if_ixml_document.
    DATA: node      TYPE REF TO if_ixml_node,
          iterator TYPE REF TO if_ixml_node_iterator,
          nodemap   TYPE REF TO if_ixml_named_node_map,
          attr      TYPE REF TO if_ixml_node,
          name      TYPE string,
          prefix    TYPE string,
          value     TYPE string,
          indent    TYPE i,
          count     TYPE i,
          index     TYPE i.
    node ?= document.
    CHECK NOT node IS INITIAL.
    ULINE.
    WRITE: /.
    WRITE: /' DOM-TREE'.
    WRITE: /.
    IF node IS INITIAL. EXIT. ENDIF.
*   create a node iterator
    iterator = node->create_iterator( ).
*   get current node
    node = iterator->get_next( ).
*   loop over all nodes
    WHILE NOT node IS INITIAL.
      indent = node->get_height( ) * 2.
      indent = indent + 20.
      CASE node->get_type( ).
        WHEN if_ixml_node=>co_node_element.
*         element node
          name    = node->get_name( ).
          nodemap = node->get_attributes( ).
          WRITE: / 'ELEMENT :'.
          WRITE: AT indent name COLOR COL_POSITIVE INVERSE.
          IF NOT nodemap IS INITIAL.
*           attributes
            count = nodemap->get_length( ).
            DO count TIMES.
              index = sy-index - 1.
              attr   = nodemap->get_item( index ).
              name   = attr->get_name( ).
              prefix = attr->get_namespace_prefix( ).
              value = attr->get_value( ).
              WRITE: / 'ATTRIBUTE:'.
              WRITE: AT indent name COLOR COL_HEADING INVERSE, '=',
                               value COLOR COL_TOTAL   INVERSE.
            ENDDO.
          ENDIF.
        WHEN if_ixml_node=>co_node_text OR
             if_ixml_node=>co_node_cdata_section.
*         text node
          value = node->get_value( ).
          WRITE: / 'VALUE     :'.
          WRITE: AT indent value COLOR COL_GROUP INVERSE.
      ENDCASE.
*     advance to next node
      node = iterator->get_next( ).
    ENDWHILE.
ENDFORM.                    "process_dom
reward points if it is use fulll ....
Girish

How to handle tables data in XML schema based adobe form

Hi all,
I am working on the CRM business partner creation by using Interactive adobe form with following steps:
1) Uploaded the offline Interactive adobe form to online interactive adobe form via WebDynpro ABAP;
2) Capture XML data into corresponding BAPI structures;
3) Save all the changes to database via BAPI.
The adobe form contains customer information as well as several table views which are bind with the context created in WebDynpro: Node NEW_BP_NODE cardinality 1:1 with single attributes and table type attributes (1:n): COLOUR_COMP, MEN_COMP etc.
While converting the xml format data to SAP context format, It is fine to use following routine to find the single attribute and map to the BAPI structure to do the database update.
NODE = DOCUMENT->FIND_FROM_NAME( NAME = 'XYZu2019).
XYZ = NODE->GET_VALUE( ).
Question: how to convert the xml table data to SAP context format in WebDynpro ABAP?
The XML table data looks like below.
<?xml version="1.0" encoding="UTF-8" ?>
<NEW_BP_NODE>
<COLOUR_COMP>
<DATA>
<ZZTFLD0W2AQW />
<ZZTFLDRZ2AQX>000</ZZTFLDRZ2AQX>
<ZZTFLDVD2TQW />
<ZZTFLDQK2HQX />
<ZZTFLDEL2XQX />
<ZZTFLDTC2DQX>000</ZZTFLDTC2DQX>
<ZZTFLDOR2UQX />
</DATA>
<DATA>
<ZZTFLD0W2AQW />
<ZZTFLDRZ2AQX />
<ZZTFLDVD2TQW />
<ZZTFLDQK2HQX />
<ZZTFLDEL2XQX />
<ZZTFLDTC2DQX />
<ZZTFLDOR2UQX />
</DATA>
<DATA>
<ZZTFLD0W2AQW />
<ZZTFLDRZ2AQX />
<ZZTFLDVD2TQW />
<ZZTFLDQK2HQX />
<ZZTFLDEL2XQX />
<ZZTFLDTC2DQX />
<ZZTFLDOR2UQX />
</DATA>
</COLOUR_COMP>
<MEN_COMP>
<DATA>
<ZZTFLD4V2V7V />
<ZZTFLDYD2N7W>000</ZZTFLDYD2N7W>
<ZZTFLDX32I7W />
<ZZTFLD2D2W7W />
<ZZTFLDGD2A7W />
</DATA>
<DATA>
<ZZTFLD4V2V7V />
<ZZTFLDYD2N7W>000</ZZTFLDYD2N7W>
<ZZTFLDX32I7W />
<ZZTFLD2D2W7W />
<ZZTFLDGD2A7W />
</DATA>
</MEN_COMP>
Thanks in advance for your help.
Michelle

Hi,
Just follow these steps:
1. Create interactive form UI element in your view.
2. Now provide Datasource and PDFSOURCE to it in form properties.
3. Now give a template name prefix with 'Z' or 'Y'.
4. Double click on it. It will prompt for interface name.
5. Provide interface name prefixed with 'Z' or 'Y'.
6. Click on Context button in the Pop up window and provide the node you have selected as DATASOURCE.
7. Click ok and it will open the form designer.
8. In this way you can create a XML Schema based Form.
9. Activate the interface and design the form providing layout type and other details.
Hope it will help.
Regards,
Vaibhav

Data Insertion, XML Schema Specifying Element minOccurs="1

An XML schema having an element with attribute minOccurs="1" has been successfully registered. A table was created based on that schema. Inserting data both with and without that element works successfully. Why is this?

The only thing right now, I can think of, is that the database doesn't recognize it as being controlled via / depends on a registered XML Schema. See the FAQ on this forum for examples (See here: How does XML DB handle XML Schema Validation ?

[11g] XML Schema full validation with binary XML ?

Hi,
Oracle's doc quotes " Loading XML data into XML schema-based binary XML storage causes full validation against the target XML schemas. ".
After registering this XML Schema which indicates that a company must have at least a code, name and pilotes element :
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xdb="http://xmlns.oracle.com/xdb"
xdb:storeVarrayAsTable="true" version="1.0">
<xsd:element name="compagnie" type="compagnieType"/>
<xsd:complexType name="compagnieType">
<xsd:sequence>
<xsd:element name="comp" type="compType" minOccurs="1" xdb:SQLName="COMP"/>
<xsd:element name="pilotes" type="pilotesType" minOccurs="1" xdb:SQLName="PILOTES"/>
<xsd:element name="nomComp" type="nomCompType" minOccurs="1" xdb:SQLName="NOMCOMP"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="pilotesType">
<xsd:sequence>
<xsd:element minOccurs="1" maxOccurs="unbounded"
name="pilote" type="piloteType" xdb:SQLName="PILOTE"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="piloteType">
<xsd:sequence>
<xsd:element name="nom" type="nomType" xdb:SQLName="NOM"/>
<xsd:element name="salaire" type="salaireType" minOccurs="0"
     xdb:SQLName="SALAIRE"/>
</xsd:sequence>
<xsd:attribute name="brevet" xdb:SQLName="BREVET">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1"/>
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
I can therefore insert a row no valid into this table
CREATE TABLE compagnie_binaryXML_grammaire OF XMLType
XMLTYPE STORE AS BINARY XML
XMLSCHEMA "http://www.soutou.net/compagnies3.xsd"
ELEMENT "compagnie"
ALLOW NONSCHEMA
VIRTUAL COLUMNS (vircolcomp AS (EXTRACTVALUE(OBJECT_VALUE,'/compagnie/comp')));
SQL> INSERT INTO compagnie_binaryXML_grammaire VALUES
2 (XMLTYPE.CREATEXML('<?xml version="1.0" encoding="ISO-8859-1"?>
3 <compagnie>
4 <pilotes></pilotes>
5 <nomComp>No pilot and no comp!</nomComp>
6 </compagnie>').CREATESCHEMABASEDXML('http://www.soutou.net/compagnies3.xsd'
1 ligne crÚÚe.
Unless the following instruction is done, no valid XML file can be added.
ALTER TABLE compagnie_binaryXML_grammaire
     ADD CONSTRAINT valide_compagniebinaryXML
     CHECK (XMLIsValid(OBJECT_VALUE) = 1);
Where is the difference between the behaviour of an object-relational table ?

My guess is that the virtual column spoils the soup (could you check).
The following works for me on 11.1.0.6.0.
connect / as sysdba
drop user test cascade;
create user test identified by test;
grant xdbadmin, dba to test;
connect test/test
spool encoding_test01.txt
var schemaPath varchar2(256)
var schemaURL varchar2(256)
set long 100000000
col SCHEMA_URL FOR a60
col object_name for a50
select * from v$version;
purge recyclebin;
alter session set recyclebin=OFF;
drop table VALIDATE_XML_SCHEMA;
prompt Create Folder for TEST schema, user
declare
   retb boolean;
begin
retb := dbms_xdb.createfolder('/test');
end;
prompt =================================================================
prompt Register Relational XML SChema
prompt =================================================================
prompt XML SChema
begin
:schemaURL := 'http://www.relational.com/root.xsd';
:schemaPath := '/test/root_relational.xsd';
end;
prompt Cleaning up
call DBMS_XMLSCHEMA.deleteSchema(:schemaURL,4);
commit;
prompt XSD Schema
declare
res boolean;
xmlSchema xmlType := xmlType(
'<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
            xmlns:xdb="http://xmlns.oracle.com/xdb"
            xmlns="http://www.relational.com/root.xsd" targetNamespace="http://www.relational.com/root.xsd"
            elementFormDefault="qualified"
            attributeFormDefault="unqualified"
            xdb:storeVarrayAsTable="true">
     <xs:element name="ROOT" xdb:defaultTable="ROOT_TABLE" xdb:maintainDOM="false">
          <xs:annotation>
               <xs:documentation>Example XML Schema</xs:documentation>
          </xs:annotation>
          <xs:complexType xdb:maintainDOM="false">
               <xs:sequence>
                    <xs:element name="ID" type="xs:integer" xdb:SQLName="ID"/>
                    <xs:element ref="INFO"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="INFO" xdb:SQLName="INFO_TYPE">
          <xs:complexType xdb:maintainDOM="false">
               <xs:sequence>
                    <xs:element name="INFO_ID" type="xs:integer" xdb:SQLName="TYPE_INFO_ID"/>
                    <xs:element name="INFO_CONTENT"
                xdb:SQLName="TYPE_INFO_CONTENT" type="xs:string"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
</xs:schema>');
begin
if (dbms_xdb.existsResource(:schemaPath)) then
    dbms_xdb.deleteResource(:schemaPath);
end if;
res := dbms_xdb.createResource(:schemaPath,xmlSchema);
end;
alter session set events='31098 trace name context forever';
BEGIN
DBMS_XMLSCHEMA.registerSchema
(SCHEMAURL => :schemaURL,
SCHEMADOC => xdbURIType(:schemaPath).getClob(),
LOCAL     => TRUE,   -- local
GENTYPES => FALSE, -- generate object types
GENBEAN   => FALSE, -- no java beans
GENTABLES => FALSE, -- generate object tables
OWNER     => USER);
END;
commit;
prompt =================================================================
prompt Register Binary XML SChema
prompt =================================================================
prompt XML SChema
begin
:schemaURL := 'http://www.binary.com/root.xsd';
:schemaPath := '/test/root_binary.xsd';
end;
prompt Cleaning up
call DBMS_XMLSCHEMA.deleteSchema(:schemaURL,4);
commit;
prompt XSD Schema
declare
res boolean;
xmlSchema xmlType := xmlType(
'<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
            xmlns:xdb="http://xmlns.oracle.com/xdb"
            xmlns="http://www.binary.com/root.xsd" targetNamespace="http://www.binary.com/root.xsd"
            elementFormDefault="qualified"
            attributeFormDefault="unqualified"
            xdb:storeVarrayAsTable="true">
     <xs:element name="ROOT" xdb:defaultTable="ROOT_TABLE" xdb:maintainDOM="false">
          <xs:annotation>
               <xs:documentation>Example XML Schema</xs:documentation>
          </xs:annotation>
          <xs:complexType xdb:maintainDOM="false">
               <xs:sequence>
                    <xs:element name="ID" type="xs:integer" xdb:SQLName="ID"/>
                    <xs:element ref="INFO"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="INFO" xdb:SQLName="INFO_TYPE">
          <xs:complexType xdb:maintainDOM="false">
               <xs:sequence>
                    <xs:element name="INFO_ID" type="xs:integer" xdb:SQLName="TYPE_INFO_ID"/>
                    <xs:element name="INFO_CONTENT"
                xdb:SQLName="TYPE_INFO_CONTENT" type="xs:string"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
</xs:schema>');
begin
if (dbms_xdb.existsResource(:schemaPath)) then
    dbms_xdb.deleteResource(:schemaPath);
end if;
res := dbms_xdb.createResource(:schemaPath,xmlSchema);
end;
alter session set events='31098 trace name context forever';
BEGIN
DBMS_XMLSCHEMA.registerSchema
(SCHEMAURL => :schemaURL,
SCHEMADOC => xdbURIType(:schemaPath).getClob(),
LOCAL     => TRUE,   -- local
GENTYPES => FALSE, -- generate object types
GENBEAN   => FALSE, -- no java beans
GENTABLES => FALSE, -- generate object tables
OPTIONS   => DBMS_XMLSCHEMA.REGISTER_BINARYXML,
OWNER     => USER);
END;
commit;
prompt =================================================================
prompt Register SECOND Binary XML SChema
prompt =================================================================
prompt XML SChema
begin
:schemaURL := 'http://www.different.com/roots.xsd';
:schemaPath := '/test/roots.xsd';
end;
prompt Cleaning up
call DBMS_XMLSCHEMA.deleteSchema(:schemaURL,4);
commit;
prompt XSD Schema
declare
res boolean;
xmlSchema xmlType := xmlType(
'<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
            xmlns:xdb="http://xmlns.oracle.com/xdb"
            xmlns="http://www.different.com/roots.xsd" targetNamespace="http://www.different.com/roots.xsd"
            elementFormDefault="qualified"
            attributeFormDefault="unqualified"
            xdb:storeVarrayAsTable="true">
     <xs:element name="ROOTS" xdb:maintainDOM="false">
          <xs:annotation>
               <xs:documentation>Example XML Schema</xs:documentation>
          </xs:annotation>
          <xs:complexType xdb:maintainDOM="false">
               <xs:sequence>
                    <xs:element name="ID" type="xs:integer" xdb:SQLName="ID"/>
                    <xs:element ref="INFO"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="INFO" xdb:SQLName="INFO_TYPE">
          <xs:complexType xdb:maintainDOM="false">
               <xs:sequence>
                    <xs:element name="INFO_ID" type="xs:integer" xdb:SQLName="TYPE_INFO_ID"/>
                    <xs:element name="INFO_CONTENT"
                xdb:SQLName="TYPE_INFO_CONTENT" type="xs:string"/>
               </xs:sequence>          </xs:complexType>
     </xs:element>
</xs:schema>');
begin
if (dbms_xdb.existsResource(:schemaPath)) then
    dbms_xdb.deleteResource(:schemaPath);
end if;
res := dbms_xdb.createResource(:schemaPath,xmlSchema);
end;
alter session set events='31098 trace name context forever';
BEGIN
DBMS_XMLSCHEMA.registerSchema
(SCHEMAURL => :schemaURL,
SCHEMADOC => xdbURIType(:schemaPath).getClob(),
LOCAL     => TRUE,   -- local
GENTYPES => FALSE, -- generate object types
GENBEAN   => FALSE, -- no java beans
GENTABLES => FALSE, -- generate object tables
OPTIONS   => DBMS_XMLSCHEMA.REGISTER_BINARYXML,
OWNER     => USER);
END;
commit;
prompt =================================================================
prompt END Registration Process
prompt =================================================================
select xmlType(xdbURIType ('/test/root.xsd').getClob())
from   dual;
alter session set events='31098 trace name context forever';
select schema_url, binary
from   user_xml_schemas;
select * from tab;
select object_name, object_type from user_objects;
prompt =================================================================
prompt BASICFILE - XMLSCHEMA (default) - DISALLOW NONSCHEMA
prompt =================================================================
drop table "VALIDATE_XML_SCHEMA";
create table "VALIDATE_XML_SCHEMA" of XMLTYPE
XMLTYPE STORE AS BASICFILE BINARY XML
XMLSCHEMA "http://www.binary.com/root.xsd"
ELEMENT "ROOT";
prompt No schema defined
insert into "VALIDATE_XML_SCHEMA"
values
(xmltype('<?xml version="1.0" encoding="UTF-8"?>
<ROOT>
<ID>0</ID>
<INFO>
    <INFO_ID>0</INFO_ID>
    <INFO_CONTENT>Text</INFO_CONTENT>
</INFO>
</ROOT>'))
prompt Bogus, noexistent schema defined
insert into "VALIDATE_XML_SCHEMA"
values
(xmltype('<?xml version="1.0" encoding="UTF-8"?>
<ROOT xmlns="http://www.bogus.com/root.xsd">
<ID>0</ID>
<INFO>
    <INFO_ID>0</INFO_ID>
    <INFO_CONTENT>Text</INFO_CONTENT>
</INFO>
</ROOT>'))
prompt Binary schema defined
insert into "VALIDATE_XML_SCHEMA"
values
(xmltype('<?xml version="1.0" encoding="UTF-8"?>
<ROOT xmlns="http://www.binary.com/root.xsd">
<ID>0</ID>
<INFO>
    <INFO_ID>0</INFO_ID>
    <INFO_CONTENT>Text</INFO_CONTENT>
</INFO>
</ROOT>'))
prompt Binary schema with different location path
insert into "VALIDATE_XML_SCHEMA"
values
(xmltype('<?xml version="1.0" encoding="UTF-8"?>
<ROOTS xmlns="http://www.different.com/roots.xsd">
<ID>0</ID>
<INFO>
    <INFO_ID>0</INFO_ID>
    <INFO_CONTENT>Text</INFO_CONTENT>
</INFO>
</ROOTS>'))
prompt Binary schema with incorrect "root(s)"
insert into "VALIDATE_XML_SCHEMA"
values
(xmltype('<?xml version="1.0" encoding="UTF-8"?>
<ROOT xmlns="http://www.different.com/roots.xsd">
<ID>0</ID>
<INFO>
    <INFO_ID>0</INFO_ID>
    <INFO_CONTENT>Text</INFO_CONTENT>
</INFO>
</ROOT>'))
prompt Relational registered schema
insert into "VALIDATE_XML_SCHEMA"
values
(xmltype('<?xml version="1.0" encoding="UTF-8"?>
<ROOT xmlns="http://www.relational.com/root.xsd">
<ID>0</ID>
<INFO>
    <INFO_ID>0</INFO_ID>
    <INFO_CONTENT>Text</INFO_CONTENT>
</INFO>
</ROOT>'))
prompt =================================================================
prompt BASICFILE - XMLSCHEMA - ALLOW NONSCHEMA
prompt =================================================================
drop table "VALIDATE_XML_SCHEMA";
create table "VALIDATE_XML_SCHEMA" of XMLTYPE
XMLTYPE STORE AS BASICFILE BINARY XML
XMLSCHEMA "http://www.binary.com/root.xsd"
ELEMENT "ROOT"
ALLOW NONSCHEMA;
prompt No schema defined
insert into "VALIDATE_XML_SCHEMA"
values
(xmltype('<?xml version="1.0" encoding="UTF-8"?>
<ROOT>
<ID>0</ID>
<INFO>
    <INFO_ID>0</INFO_ID>
    <INFO_CONTENT>Text</INFO_CONTENT>
</INFO>
</ROOT>'))
prompt Bogus, noexistent schema defined
insert into "VALIDATE_XML_SCHEMA"
values
(xmltype('<?xml version="1.0" encoding="UTF-8"?>
<ROOT xmlns="http://www.bogus.com/root.xsd">
<ID>0</ID>
<INFO>
    <INFO_ID>0</INFO_ID>
    <INFO_CONTENT>Text</INFO_CONTENT>
</INFO>
</ROOT>'))
prompt Binary schema defined
insert into "VALIDATE_XML_SCHEMA"
values
(xmltype('<?xml version="1.0" encoding="UTF-8"?>
<ROOT xmlns="http://www.binary.com/root.xsd">
<ID>0</ID>
<INFO>
    <INFO_ID>0</INFO_ID>
    <INFO_CONTENT>Text</INFO_CONTENT>
</INFO>
</ROOT>'))
prompt Binary schema with different location path
insert into "VALIDATE_XML_SCHEMA"
values
(xmltype('<?xml version="1.0" encoding="UTF-8"?>
<ROOTS xmlns="http://www.different.com/roots.xsd">
<ID>0</ID>
<INFO>
    <INFO_ID>0</INFO_ID>
    <INFO_CONTENT>Text</INFO_CONTENT>
</INFO>
</ROOTS>'))
prompt Binary schema with incorrect "root(s)"
insert into "VALIDATE_XML_SCHEMA"
values
(xmltype('<?xml version="1.0" encoding="UTF-8"?>
<ROOT xmlns="http://www.different.com/roots.xsd">
<ID>0</ID>
<INFO>
    <INFO_ID>0</INFO_ID>
    <INFO_CONTENT>Text</INFO_CONTENT>
</INFO>
</ROOT>'))
prompt Relational registered schema
insert into "VALIDATE_XML_SCHEMA"
values
(xmltype('<?xml version="1.0" encoding="UTF-8"?>
<ROOT xmlns="http://www.relational.com/root.xsd">
<ID>0</ID>
<INFO>
    <INFO_ID>0</INFO_ID>
    <INFO_CONTENT>Text</INFO_CONTENT>
</INFO>
</ROOT>'))
-- Output
BANNER
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
PL/SQL Release 11.1.0.6.0 - Production
CORE     11.1.0.6.0     Production
TNS for 32-bit Windows: Version 11.1.0.6.0 - Production
NLSRTL Version 11.1.0.6.0 - Production
5 rows selected.
Recyclebin purged.
Session altered.
drop table VALIDATE_XML_SCHEMA
ERROR at line 1:
ORA-00942: table or view does not exist
Create Folder for TEST schema, user
declare
ERROR at line 1:
ORA-31003: Parent / already contains child entry test
ORA-06512: at "XDB.DBMS_XDB", line 316
ORA-06512: at line 4
=================================================================
Register Relational XML SChema
=================================================================
XML SChema
PL/SQL procedure successfully completed.
Cleaning up
call DBMS_XMLSCHEMA.deleteSchema(:schemaURL,4)
ERROR at line 1:
ORA-31000: Resource 'http://www.relational.com/root.xsd' is not an XDB schema document
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 106
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 102
ORA-06512: at line 1
Commit complete.
XSD Schema
PL/SQL procedure successfully completed.
Session altered.
PL/SQL procedure successfully completed.
Commit complete.
=================================================================
Register Binary XML SChema
=================================================================
XML SChema
PL/SQL procedure successfully completed.
Cleaning up
call DBMS_XMLSCHEMA.deleteSchema(:schemaURL,4)
ERROR at line 1:
ORA-31000: Resource 'http://www.binary.com/root.xsd' is not an XDB schema document
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 106
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 102
ORA-06512: at line 1
Commit complete.
XSD Schema
PL/SQL procedure successfully completed.
Session altered.
PL/SQL procedure successfully completed.
Commit complete.
=================================================================
Register SECOND Binary XML SChema
=================================================================
XML SChema
PL/SQL procedure successfully completed.
Cleaning up
call DBMS_XMLSCHEMA.deleteSchema(:schemaURL,4)
ERROR at line 1:
ORA-31000: Resource 'http://www.different.com/roots.xsd' is not an XDB schema document
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 106
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 102
ORA-06512: at line 1
Commit complete.
XSD Schema
PL/SQL procedure successfully completed.
Session altered.
PL/SQL procedure successfully completed.
Commit complete.
=================================================================
END Registration Process
=================================================================
Session altered.
SCHEMA_URL                                                   BIN
http://www.relational.com/root.xsd                           NO
http://www.binary.com/root.xsd                               YES
http://www.different.com/roots.xsd                           YES
3 rows selected.
no rows selected
no rows selected
=================================================================
BASICFILE - XMLSCHEMA (default) - DISALLOW NONSCHEMA
=================================================================
drop table "VALIDATE_XML_SCHEMA"
ERROR at line 1:
ORA-00942: table or view does not exist
Table created.
No schema defined
(xmltype('<?xml version="1.0" encoding="UTF-8"?>
ERROR at line 3:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LSX-00021: undefined element "ROOT"
Bogus, noexistent schema defined
(xmltype('<?xml version="1.0" encoding="UTF-8"?>
ERROR at line 3:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LSX-00023: unknown namespace URI "http://www.bogus.com/root.xsd"
Binary schema defined
1 row created.
Binary schema with different location path
(xmltype('<?xml version="1.0" encoding="UTF-8"?>
ERROR at line 3:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LSX-00023: unknown namespace URI "http://www.different.com/roots.xsd"
Binary schema with incorrect "root(s)"
(xmltype('<?xml version="1.0" encoding="UTF-8"?>
ERROR at line 3:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LSX-00023: unknown namespace URI "http://www.different.com/roots.xsd"
Relational registered schema
(xmltype('<?xml version="1.0" encoding="UTF-8"?>
ERROR at line 3:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LSX-00023: unknown namespace URI "http://www.relational.com/root.xsd"
=================================================================
BASICFILE - XMLSCHEMA - ALLOW NONSCHEMA
=================================================================
Table dropped.
Table created.
No schema defined
1 row created.
Bogus, noexistent schema defined
1 row created.
Binary schema defined
1 row created.
Binary schema with different location path
1 row created.
Binary schema with incorrect "root(s)"
1 row created.
Relational registered schema
1 row created.

Null value for int and datetime date type in xml schema

hi:
I am embarrassed by a qustion in xml schema; i defined a xml schema file like
this:
<elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:element name="test">
<xs:annotation>
<xs:documentation>Comment describing your root element</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="xs:string"/>
<xs:element name="password" type="xs:string" nillable="true"/>
<xs:element name="user" type="xs:int" nillable="true"/>
<xs:element name="s_time" type="xs:dateTime"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
and I send this file to workflow clientrequest() node, I wanted to receive data
in this schema file.but when i send null value to the element "user" and "s_time"
in workshop test tool(test soap),and use function in xmlbean like isNilUser or
isNilStime, one error occur.
I don't kown why, I had to ask the engineer of bea in china, one told me a bug.
is that true?

Visakh16 I cant agree more with you on it, it is good but in production u cant have them change maxrows. I think
Patrick Hurst is a better option. debug the package have it running and move up
Please mark as helpful and propose as answer if you find this as correct!!! Thanks,Dia Agha .
Hmm..Why do you need to change it in production?
What I suggested was to tweak the setting in dev machine so that it interprets the Excel file datatypes correctly when doing development. Once mapping is set correctly then it will work fine when in production or in any other environment. The tweaking is
just to make sure it interprets the datatype correctly at design time and has nothing to do with production deployment
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

XML Schema to generate table data from a repeating subform data

Hi All, I would like to have a check box that when checked, will hide a quotation form, and make a purchase order form visible, carrying over some of the field data from the quotation form into a new table on the Purchase order form. I've attached this form at https://workspaces.acrobat.com/?d=pqpsXx5VPi*LkMeVKrX57w if you would like to take a look. When the checkbox is unchecked, it will hid the PO form, and make the quite form visible.
The idea behind this is that my client will create his quote and send t to his customer. Once the customer accepts the quote, he can just click a button to generate his purchase order that he will send to his supplier.
It seems that because I've got buttons to add rows on the quote form that the problem is more complex. I would be able to do this myself if the table had a fixed number of rows and I was able to use global fields and naming each cell something different, but beacuse it's a single repeating subform, I can't seem to make it work at all.
I understand that because its a repeating subform that I need to create an XML schema to accomplish this, but also can't figure out for the life of me how to actually create the schema. I've been reading tons of tutorials, but no clue how to apply it to my specific need. I have only been able only find info on how to bind the data source once it's been created.
I would be forever grateful if anyone could help me out.
Thank you!

I've edited your form and put it here.
Here's what I've done:
Inserted script into your checkbox renamed Accpted that hides/shows the Purchase Order/ Sales Quotation
I've included a scripting object with a function I wrote to transfer data from like named fields/subforms from one section to another
Inserted a few common fields into your Purchase Order table
What you need to do is complete the development of your Purchase Order table. Make sure the common fields between the quote and purchase tables have the same names in order to transfer the data.
No schema necessary.
Kyle

Forms pulling Multiple Records from an XML Schema and XML data files - Adobe LiveCycle Designer

I built a form in Adobe LiveCycle with an xml schema and data file. The problem is with how the form renders the xml data file.
I have a statement element that consists of about 6 fields (statementID, statementName, statementAddress, statementCountry, statementZip, statementDate, etc) of data in the schema that allows for multiple iterations - so one xml data file can contain multiple statements. These fields allow for null values.
But here's the problem: When any of the statements - say statement 2 of 6 - has a null value in one of the fields, if the xml data file doesn't have a placeholder
(example of placeholder: <statementName type="String"/> )in the xml for that field, my form pulls the field value from the NEXT statement.
This corrupts all the rest of the statement records, as this field is shifted up for all the rest.
I know that in the past I haven't needed a placeholder when a field was null. But I'm wondering if when the data allows for multiple records the xml data file needs to generate the placeholder. And where is the problem? In the Schema? The xml data file? My form? And the 64-thousand-dollar question: How to fix it?

If your <statement> element is the one that repeats, it should be bound to a subform with the binding string of something like $.statement[*]. Then in that subform should be your fields and they should have bindings of $.statementID, $.statementName, $.statementAddress, etc.
Kyle

How to bind data from script created variable to embed element of XML schema (xsd) in "Data View"

Hi, i have got another problem with livecycle designer scripting.
I have got script line which is defining of string variable:
var aaa = "this is my string";
and i have got embed XML schema like this (it`s only short part of whole file):
... xs:element name="bbb" type="xs:string"/ ...
After saving data to XML i would like to get "this is my string" as a value of my "bbb" XML element.
To save this data i`m using submit button which is connect with submit.php file on my server.
How to connect script created variable and embed XML schema element which is present on my "Data View" tab.
Please help me a bit becouse i don`t know even where to search answer of it...
Of course i know possibilities to create fake unvisible text field object and bind it with 'bbb' and than put "this.rawValue = aaa" to connect those two variables but i think that is not a good idea to solve it in that way. It`s too primitive

i solve it, i should write this:
xfa.datasets.data.bbb.value = aaa;

XML Schema file in data definition

Hi,
I am creating a custom RTF template for a seeded data definition in the eBusiness Suite. The data definition has an XML Schema file loaded however this does not include all the data required for the template. Running the report to just generate the XML (i.e. no template) I can see that the additional data is available at this level just not included in the XSD.
I have built the template including the additional elements from the XML and expected to have to create a custom data definition as well to add the additional elements to the XSD. However the template is working against the seeded definition and successfully picking up the elements that are not included in the XSD.
Has anybody else come across this situation? And are there any potential issues? I could create a custom data definition as well to load an amended XSD but this would be a more invasive change as it would involve end dating the seeded data definition which I would prefer not to do. The report is not being generated from a concurrent request so I cannot just create a custom request and leave the seeded report untouched.
Thanks,
Sarah

The XML Schema is only required if you are using a PDF template (the template file itself is PDF) with field-mapping. For other template types the schema is optional.
The XML Schema is used to define a "class" of XML documents, so to speak. The define the semantics and structure of the XML documents more thoroughly.
If you have closely related reports, you could use a single schema to standardize (in a sense) the XML to be output from the class of related reports. In that case you could have a single schema file uploaded to multiple reports/data-definitions.
The W3C has good documentation on XML Schema.
If you want to see samples, you can use tools such as dtd2xs to create sample schemas from your DTD.

Insert data into the xml schema-based xmltype table problem!

Hello, there,
I got problem in inserting data into the xmltype table after registered XML schema and created table. details see below:
1) xml schema:
<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.emergis.com/eHealth/EHIP/data/meta/profile:v1" targetNamespace="http://www.emergis.com/eHealth/EHIP/data/meta/profile:v1" elementFormDefault="qualified">
     
     <xs:simpleType name="RoutingType">
          <xs:restriction base="xs:string">
               <xs:enumeration value="Synch"/>
               <xs:enumeration value="Asynch"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="StatusType">
          <xs:restriction base="xs:string">
               <xs:enumeration value="ACTIVE"/>
               <xs:enumeration value="VOID"/>
               <xs:enumeration value="PENDING"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="SenderApplicationType">
          <xs:restriction base="xs:string">
               <xs:enumeration value="PR"/>
               <xs:enumeration value="CR"/>
               <xs:enumeration value="POS"/>
               <xs:enumeration value="CPP"/>
               <xs:enumeration value="Other"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="ServiceTypeType">
          <xs:restriction base="xs:string">
               <xs:enumeration value="IS"/>
               <xs:enumeration value="WS"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="RouteDirect">
          <xs:restriction base="xs:string">
               <xs:enumeration value="Request"/>
               <xs:enumeration value="Reply"/>
               <xs:enumeration value="None"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="Indicator">
          <xs:annotation>
               <xs:documentation>can we also change the value to "ON" and "OFF" instead? in this way this cn be shared by all type of switch indicator</xs:documentation>
          </xs:annotation>
          <xs:restriction base="xs:string">
               <xs:enumeration value="YES"/>
               <xs:enumeration value="NO"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="RuleType">
          <xs:restriction base="xs:string">
               <xs:enumeration value="ControlAct"/>
               <xs:enumeration value="WSPolicy"/>
               <xs:enumeration value="AccessControl"/>
               <xs:enumeration value="Certification"/>
               <xs:enumeration value="MessageConformance"/>
               <xs:enumeration value="Variant"/>
               <xs:enumeration value="Routing"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="HL7Result">
          <xs:restriction base="xs:string">
               <xs:enumeration value="ACCEPT"/>
               <xs:enumeration value="REFUSE"/>
               <xs:enumeration value="REJECT"/>
               <xs:enumeration value="ACK"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="IIPType">
          <xs:restriction base="xs:string">
               <xs:enumeration value="PUT"/>
               <xs:enumeration value="GET/LIST"/>
               <xs:enumeration value="NOTIF"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="ProfileTypeType">
          <xs:restriction base="xs:string">
               <xs:enumeration value="IIPProfile"/>
               <xs:enumeration value="BizOperationProfile"/>
               <xs:enumeration value="OrchestrationProfile"/>
               <xs:enumeration value="DomainObjectProfile"/>
               <xs:enumeration value="ServiceProfile"/>
               <xs:enumeration value="ExceptionProfile"/>
               <xs:enumeration value="CustomizedProfile"/>
               <xs:enumeration value="SystemProfile"/>
               <xs:enumeration value="HL7XMLSchemaProfile"/>
               <xs:enumeration value="EnricherParametersProfile"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="ParameterType">
          <xs:restriction base="xs:string">
               <xs:enumeration value="String"/>
               <xs:enumeration value="Object"/>
               <xs:enumeration value="Number"/>
               <xs:enumeration value="Document"/>
          </xs:restriction>
     </xs:simpleType>
     
     
     
     <xs:complexType name="ProfileType">
          <xs:annotation>
               <xs:documentation>
          1.Profile IS USED TO BE AN WRAPPER ELEMENT FOR ALL KIND OF PROFILES NO MATTER WHAT KIND OF PROFILE IT IS
          2.ProfileID used to uniquely identify the current profile
          3.ProfileData used to hold all the necessary profile related data
          </xs:documentation>
          </xs:annotation>
          <xs:sequence>
               <xs:element name="ProfileID" type="ProfileIDType">
                    <xs:annotation>
                         <xs:documentation>this will hold all the common attributes, espically the global unique identifier to the profile, no matter what type of profile is</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="ProfileData" type="ProfileDataType">
                    <xs:annotation>
                         <xs:documentation>all the non-common profile meta data that attached to each specific profile type such as IIPProfile, OrchestrationProfile, and BizOperationProfile will be placed here</xs:documentation>
                    </xs:annotation>
               </xs:element>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="ProfileIDType">
          <xs:annotation>
               <xs:documentation>global unique identifier and all the common attributes across all different profiles, the @ID and @Type together will be used as the primary key to identify the profile data</xs:documentation>
          </xs:annotation>
          <xs:attribute name="ID" type="xs:ID" use="required">
               <xs:annotation>
                    <xs:documentation>ID is the global unique identifier to the profile, no matter what type of profile it is</xs:documentation>
               </xs:annotation>
          </xs:attribute>
          <xs:attribute name="Name"/>
          <xs:attribute name="Description"/>
          <xs:attribute name="Version">
               <xs:annotation>
                    <xs:documentation>version of the profile data</xs:documentation>
               </xs:annotation>
          </xs:attribute>
          <xs:attribute name="Type" type="ProfileTypeType" use="required">
               <xs:annotation>
                    <xs:documentation>value to identify the ProfileType type within
                    IIPProfile,BizOperationProfile,OrchestrationProfile,DomainObjectProfile
                    ServiceProfile,ExceptionProfile,SystemProfile,HL7XMLSchemaProfile,
                    EnricherParametersProfile,CustomizedProfile
                    </xs:documentation>
               </xs:annotation>
          </xs:attribute>
          <xs:attribute name="Status" type="StatusType" default="ACTIVE">
               <xs:annotation>
                    <xs:documentation>used to show the related profile data status like "ACTIVE","PENDING","VOID"...</xs:documentation>
               </xs:annotation>
          </xs:attribute>
          
     </xs:complexType>
     <xs:complexType name="ProfileDataType">
          <xs:annotation>
               <xs:documentation>meta data associated tightly to each specific type of profile</xs:documentation>
          </xs:annotation>
          <xs:choice>
               <xs:element name="EnricherParametersProfileData" type="EnricherParametersDataType">
                    <xs:annotation>
                         <xs:documentation>Enricher Parameters related profile data
               1. one instance of this type may contains all the related System metadata.
               2. idType part may use to identify different version/release/status
               </xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="ExtendProfileData" type="ExtendProfileDataType">
                    <xs:annotation>
                         <xs:documentation>If needed, any profile data not defined within the current release scope can be added here </xs:documentation>
                    </xs:annotation>
               </xs:element>
          </xs:choice>
     </xs:complexType>
     <xs:complexType name="ExtendProfileDataType">
          <xs:sequence>
               <xs:element name="ExtendProfile" type="xs:anyType" minOccurs="0"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="EnricherParametersDataType">
          <xs:sequence>
               <xs:element name="EnricherParameter" type="EnricherParameter" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="EnricherParameter">
          <xs:sequence>
               <xs:element ref="Enricher"/>
          </xs:sequence>
          <xs:attribute name="serviceName" type="xs:string" use="required"/>
          <xs:attribute name="interactionID" type="xs:string"/>
     </xs:complexType>
     <xs:element name="Enricher">
          <xs:annotation>
               <xs:documentation>Comment describing your root element</xs:documentation>
          </xs:annotation>
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="Parameters" type="Parameters"/>
                    <xs:element ref="Section" maxOccurs="unbounded"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:complexType name="ValueType">
          <xs:attribute name="field" use="required"/>
          <xs:attribute name="value"/>
          <xs:attribute name="action"/>
     </xs:complexType>
     <xs:element name="Section">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="Value" type="ValueType" minOccurs="0" maxOccurs="unbounded"/>
                    <xs:element ref="Section" minOccurs="0" maxOccurs="unbounded"/>
               </xs:sequence>
               <xs:attribute name="path" use="required"/>
          </xs:complexType>
     </xs:element>
     <xs:complexType name="Parameters">
          <xs:sequence>
               <xs:element name="Parameter" minOccurs="0" maxOccurs="unbounded">
                    <xs:complexType>
                         <xs:attribute name="name" use="required"/>
                         <xs:attribute name="reference"/>
                    </xs:complexType>
               </xs:element>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="RuleList">
          <xs:annotation>
               <xs:documentation>an array of rules</xs:documentation>
          </xs:annotation>
          <xs:sequence>
               <xs:element name="Rule" type="RuleProfile" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="RuleProfile">
          <xs:attribute name="RName" use="required"/>
          <xs:attribute name="RType" type="RuleType" use="required"/>
          <xs:attribute name="Status" default="ON">
               <xs:annotation>
                    <xs:documentation>By default is ON (or if is missing)</xs:documentation>
               </xs:annotation>
          </xs:attribute>
          <xs:attribute name="Order"/>
          <xs:attribute name="Direction" type="RouteDirect">
               <xs:annotation>
                    <xs:documentation>Request / Reply</xs:documentation>
               </xs:annotation>
          </xs:attribute>
     </xs:complexType>
     
     
     
     <xs:element name="Profile" type="ProfileType">
          <xs:annotation>
               <xs:documentation>Profile IS USED TO BE AN WRAPPER ELEMENT FOR ALL KIND OF PROFILES NO MATTER WHAT KIND OF PROFILE IT IS</xs:documentation>
          </xs:annotation>
     </xs:element>
</xs:schema>
2)register xml schema:
SQL> begin
2 dbms_xmlschema.registerSchema
3 (
4 schemaurl=>'http://rac3-1-vip:8080/home/'||USER||'/xsd/EHIPProfile_v00.xsd',
5 schemadoc=>xdbURIType('/home/'||USER||'/xsd/EHIPProfile_v00.xsd').getClob(),
6 local=>True,
7 gentypes=>True,
8 genbean=>False,
9 gentables=>False
10 );
11 End;
12 /
PL/SQL procedure successfully completed.
SQL>
SQL>
3) xml data:
<?xml version="1.0" encoding="UTF-8"?>

<Profile xmlns="http://www.emergis.com/eHealth/EHIP/data/meta/profile:v1">
     <ProfileID Type="EnricherParametersProfile" Status="ACTIVE" ID="EnricherPP.ID.0001" Name="EnricherPP.ID.0001" Description="EnricherPP.ID.0001" Version="01"/>
     <ProfileData>
          <EnricherParametersProfileData>
               <EnricherParameter serviceName="LRS_BusinessDomainObject.lrs.businessDomainObject.domainObjectBuilder.concrete.ExceptionCreators:createExceptionV50CategoryCanonicalPart" interactionID="">
               <Enricher>
                    <Parameters>
                         <Parameter name="MESSAGE_ID" reference="test"/>
                    </Parameters>
                    <Section path="HEADER">
                         <Section path="RESPONSE_TYPE">
                              <Value field="value" value="I"/>
                         </Section>
                         <Section path="HL7_STANDARD_VERSION">
                              <Value field="value" value="HL7V3"/>
                         </Section>
                         <Section path="DESIRED_ACKNOWLEDGMENT_TYPE">
                              <Value field="value" value="NE"/>
                         </Section>
                         <Section path="SENDING_NETWORK_ADDRESS">
                              <Value field="value" value=""/>
                         </Section>
                         <Section path="SENDING_APPLICATION_IDENTIFIER">
                              <Value field="root" value="2.16.840.1.113883.3.133.1.3"/>
                              <Value field="extension" value=""/>
                         </Section>
                         <Section path="SENDING_APPLICATION_NAME">
                              <Value field="value" value="NL HIAL"/>
                         </Section>
                    </Section>
               </Enricher>
     </EnricherParameter>
          <EnricherParameter serviceName="LRS_BusinessDomainObject.lrs.businessDomainObject.domainObjectBuilder.concrete.DomainObjectCreators:createFindClientsAssociatedIdentifersRequestObject" interactionID="PRPA_IN101105CA">
               <Enricher>
                    <Parameters>
                         <Parameter name="MESSAGE_ID" reference="test"/>
                    </Parameters>
                    <Section path="HEADER">
                         <Section path="RESPONSE_TYPE">
                              <Value field="value" value="I"/>
                         </Section>
                         <Section path="HL7_STANDARD_VERSION">
                              <Value field="value" value="HL7V3"/>
                         </Section>
                         <Section path="PROCESSING_CODE">
                              <Value field="value" value="T"/>
                         </Section>
                         
                         <Section path="DESIRED_ACKNOWLEDGMENT_TYPE">
                              <Value field="value" value="NE"/>
                         </Section>
                         <Section path="RECEIVER_NETWORK_ADDRESS">
                              <Value field="value" value="prsunew.moh.hnet.bc.ca"/>
                         </Section>
                         <Section path="RECEIVER_APPLICATION_IDENTIFIER">
                              <Value field="root" value="2.16.840.1.113883.3.40.5.1"/>
                              <Value field="extension" value=""/>
                         </Section>
                         <Section path="SENDING_NETWORK_ADDRESS">
                              <Value field="value" value=""/>
                         </Section>
                         <Section path="SENDING_APPLICATION_IDENTIFIER">
                              <Value field="root" value="2.16.840.1.113883.3.133.1.3"/>
                              <Value field="extension" value=""/>
                         </Section>
                         <Section path="SENDING_APPLICATION_NAME">
                              <Value field="value" value="NL HIAL"/>
                         </Section>
                    </Section>
               </Enricher>
     </EnricherParameter>
          <EnricherParameter serviceName="LRS_BusinessDomainObject.lrs.businessDomainObject.domainObjectBuilder.concrete.DomainObjectContentEnrichers:enrichPRRequest" interactionID="">

<Enricher>
     <Parameters>
          <Parameter name="MESSAGE_IDENTIFIER" reference="test"/>
     </Parameters>
     <Section path="HEADER">
          <Section path="HL7_STANDARD_VERSION">
               <Value field="value" value="V3PR2"/>
          </Section>
          
          
          <Section path="PROCESSING_CODE">
               <Value field="value" value="T"/>
          </Section>
          
          <Section path="PROCESSING_MODE_CODE">
               <Value field="value" value="T"/>
          </Section>
          
          <Section path="DESIRED_ACKNOWLEDGMENT_TYPE">
               <Value field="value" value="NE"/>
          </Section>
          
          
          <Section path="RECEIVER_APPLICATION_IDENTIFIER[0]">
               <Value field="root" value="2.16.840.1.113883.3.40.1.14"/>
               <Value field="extension" value="SIT1"/>
          </Section>
          
          <Section path="RECEIVER_APPLICATION_NAME[0]">
               <Value field="value" value="receiverAppName"/>
          </Section>
          
          
          <Section path="RECEIVER_AGENT/RECEIVER_ORGANIZATION/RECEIVER_ORGANIZATION_IDENTIFIER[0]">
               <Value field="root" value="2.16.840.1.113883.3.40.4.1"/>
               <Value field="extension" value="receiverOrgId"/>
          </Section>
          <Section path="SENDING_APPLICATION_NAME[0]">
               <Value field="value" value="NLPRSCLNT"/>
          </Section>
          
          
          <Section path="SENDING_AGENT/SENDING_ORGANIZATION/SENDING_ORGANIZATION_IDENTIFIER[0]">
               <Value field="root" value="2.16.840.1.113883.4.3.57"/>
               <Value field="extension" value="3001"/>
          </Section>
          <Section path="PERFORMER/HEALTHCARE_WORKER_IDENTIFIER[0]">
               <Value field="root" value="2.16.840.1.113883.4.3.57"/>
               <Value field="extension" value="HIAL_USR"/>
          </Section>
     </Section>
     <Section path="PAYLOAD">
          
          
          <Section path="AUDIT[0]/AUDIT_INFORMATION">
               <Value field="code" value="LATEST"/>
               <Value field="codeSystem" value="PRSAuditParameters"/>
          </Section>
          
          <Section path="CONFIDENCE/CONFIDENCE_VALUE">
               <Value field="value" value="100"/>
          </Section>
          
          <Section path="HISTORY/INCLUDE_HISTORY_INDICATOR">
               <Value field="value" value="false"/>
          </Section>
          
          <Section path="JURISDICTION/JURISDICTION_TYPE">
               <Value field="value" value="NL"/>
          </Section>
          
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[0]">
               <Value field="code" value="GRS_ADDRESS"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[1]">
               <Value field="code" value="GRS_ELECTRONIC_ADDRESS"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[2]">
               <Value field="code" value="GRS_IDENTIFIER"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[3]">
               <Value field="code" value="GRS_ORGANIZATION_NAME"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[4]">
               <Value field="code" value="GRS_PERSONAL_NAME"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[5]">
               <Value field="code" value="GRS_REGISTRY_IDENTIFIER"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[6]">
               <Value field="code" value="GRS_TELEPHONE"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[7]">
               <Value field="code" value="PRS_CONDITION"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[8]">
               <Value field="code" value="PRS_CONFIDENTIALITY_INDICATOR"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[9]">
               <Value field="code" value="PRS_DEMOGRAPHIC_DETAIL"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[10]">
               <Value field="code" value="PRS_DISCIPLINARY_ACTION"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[11]">
               <Value field="code" value="PRS_INFORMATION_ROUTE"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[12]">
               <Value field="code" value="PRS_NOTE"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[13]">
               <Value field="code" value="PRS_PROVIDER_CREDENTIAL"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[14]">
               <Value field="code" value="PRS_PROVIDER_EXPERTISE"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[15]">
               <Value field="code" value="PRS_PROVIDER_RELATIONSHIP"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[16]">
               <Value field="code" value="PRS_STATUS"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[17]">
               <Value field="code" value="PRS_WORK_LOCATION"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[18]">
               <Value field="code" value="PRS_WORK_LOCATION_ADDRESS"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[19]">
               <Value field="code" value="PRS_WORK_LOCATION_DETAIL"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[20]">
               <Value field="code" value="PRS_WORK_LOCATION_ELECTRONIC_ADDRESS"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[21]">
               <Value field="code" value="PRS_WORK_LOCATION_INFORMATION_ROUTE"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[22]">
               <Value field="code" value="PRS_WORK_LOCATION_TELEPHONE"/>
          </Section>
          
          <Section path="ROLE_CLASS /ROLE_CLASS_VALUE">
               <Value field="value" value="LIC"/>
          </Section>
          <Section path="SORT_CONTROL[0]/SORT_CONTROL_ELEMENT_NAME">
               <Value field="code" value="PrincipalPerson.name.value.family"/>
          </Section>
          <Section path="SORT_CONTROL[0]/SORT_CONTROL_DIRECTION_CODE">
               <Value field="value" value="A"/>
          </Section>
     </Section>
</Enricher>
     </EnricherParameter>
          </EnricherParametersProfileData>
     </ProfileData>
</Profile>
the data is valid against the schema through XML Spy tool... and loaded into the XDB repository...
4) create table and insert data:
SQL> CREATE TABLE EHIP_PROFILE OF SYS.XMLTYPE
2 XMLSCHEMA "http://rac3-1-vip:8080/home/EHIPSBUSER1/xsd/EHIPProfile_v00.xsd" ELEMENT "Profile"
3 ;
Table created.
SQL>
SQL> alter table EHIP_PROFILE
2 add CONSTRAINT EHIP_PROF_PK PRIMARY KEY(XMLDATA."ProfileID"."ID",XMLDATA."ProfileID"."Type");
Table altered.
SQL>
SQL>
SQL>
SQL>
SQL> select xdbURIType('/home/'||USER||'/ProfileData/EnricherPP.ID.0001.xml').getClob() from dual;
XDBURITYPE('/HOME/'||USER||'/PROFILEDATA/ENRICHERPP.ID.0001.XML').GETCLOB()
<?xml version="1.0" encoding="UTF-8"?>
<!--Sample XML file generated by XMLSpy
SQL>
SQL>
SQL> insert into ehip_profile values(xmltype.createXML(xdbURIType('/home/'||USER||'/ProfileData/EnricherPP.ID.0001.xml').getClob()));
insert into ehip_profile values(xmltype.createXML(xdbURIType('/home/'||USER||'/ProfileData/EnricherPP.ID.0001.xml').getClob()))
ERROR at line 1:
ORA-21700: object does not exist or is marked for delete
what's the problem caused the "ORA-21700: object does not exist or is marked for delete" error?
Thanks in advance for your help?

Thanks Marco,
Here're my environment:
SQL> select INSTANCE_NUMBER, INSTANCE_NAME,HOST_NAME,VERSION from v$instance;
INSTANCE_NUMBER INSTANCE_NAME HOST_NAME VERSION
2 rac32 RAC3-2 10.2.0.3.0
I followed your suggested in the above, and always purge recyclebin, but still got the same problem. because in 10gr2, there's no dbms_xmlschema.purge_schema available,
and I did checked the recyclebin after force the delete of schema, nothing inside. any other recommendation?

Can't i use xml schema and oledb data connection at the same time?

Hello to all and thanks in advance.I use xml schema and oledb data connection at the same time and the problem is that when I try to export the xml, the outcome is not what i expect.Without the oledb connection everything is ok (just the schema) and the xml complies with the schema.
Can't i have both schema and oledb and the exported xml be as i want it?

You can use both at the same time, but not gor Internet access if that's what you're asking.
Now there is a thing called Link Aggregation, which combines a number of interfaces for speed/redundancy, but it really only works locally, and then only with ALL special equipment in the route, and most likely OSX Server involved.
Sorry.

Date type in xml schema

The date type in schema processor doesn't work. I can replace the date in the xml with any character and still get the xml validated. Same problem with year and month type.

Hi,
The behaviour I posted above has been identified as a bug by Oracle and a patch(#6053186) now exists for this problem. This patch is available for database version 10.2.0.3 and the bug would eventually be fixed only in database version 11g according to the details published for the bug.
Rgds,
Rakesh.

Problem inserting and querying XML data with a recursive XML schema

Hello,
I'm facing a problem with querying XML data that is valid against a recursive XML Schema. I have got a table category that stores data as binary XML using Oracle 11g Rel 2 on Windows XP. The XML Schema is the following:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:complexType name="bold_type" mixed="true">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="bold" type="bold_type"/>
               <xs:element name="keyword" type="keyword_type"/>
               <xs:element name="emph" type="emph_type"/>
          </xs:choice>
     </xs:complexType>
     <xs:complexType name="keyword_type" mixed="true">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="bold" type="bold_type"/>
               <xs:element name="keyword" type="keyword_type"/>
               <xs:element name="emph" type="emph_type"/>
               <xs:element name="plain_text" type="xs:string"/>
          </xs:choice>
     </xs:complexType>
     <xs:complexType name="emph_type" mixed="true">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="bold" type="bold_type"/>
               <xs:element name="keyword" type="keyword_type"/>
               <xs:element name="emph" type="emph_type"/>
          </xs:choice>
     </xs:complexType>
     <xs:complexType name="text_type" mixed="true">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="bold" type="bold_type"/>
               <xs:element name="keyword" type="keyword_type"/>
               <xs:element name="emph" type="emph_type"/>
          </xs:choice>
     </xs:complexType>
     <xs:complexType name="parlist_type">
          <xs:sequence>
               <xs:element name="listitem" minOccurs="0" maxOccurs="unbounded" type="listitem_type"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="listitem_type">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="parlist" type="parlist_type"/>
               <xs:element name="text" type="text_type"/>
          </xs:choice>
     </xs:complexType>
     <xs:element name="category">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="name"/>
                    <xs:element name="description">
                              <xs:complexType>
                                        <xs:choice>
                                                       <xs:element name="text" type="text_type"/>
                                                       <xs:element name="parlist" type="parlist_type"/>
                                        </xs:choice>
                              </xs:complexType>
                    </xs:element>
                                                            </xs:sequence>
                                                            <xs:attribute name="id"/>
                                        </xs:complexType>
                    </xs:element>
</xs:schema>I registered this schema and created the category table. Then I inserted a new row using the code below:
insert into category_a values
(XMlElement("category",
      xmlattributes('categoryAAA' as "id"),
      xmlforest ('ma categ' as "name"),
      (xmlelement("description", (xmlelement("text", 'find doors blest now whiles favours carriage tailor spacious senses defect threat ope willow please exeunt truest assembly <keyword> staring travels <bold> balthasar parts attach </bold> enshelter two <emph> inconsiderate ways preventions </emph> preventions clasps better affections comes perish </keyword> lucretia permit street full meddle yond general nature whipp <emph> lowness </emph> grievous pedro')))
The row is successfully inserted as witnessed by the results of row counting. However, I cannot extract data from the table. First, I tried using SqlPlus* which hangs up and quits after a while. I then tried to use SQL Developer, but haven't got any result. Here follow some examples of queries and their results in SQL Developer:
Query 1
select * from category
Result : the whole row is returned
Query 2
select xmlquery('$p/category/description' passing object_value as "p" returning content) from category
Result: "SYS.XMLTYPE"
now I tried to fully respect the nested structure of description element in order to extract the text portion of <bold> using this query
Query 3
select xmlquery('$p/category/description/text/keyword/bold/text()' passing object_value as "p" returning content) from category_a
Result: null
and also tried to extract the text portion of element <text> using this query
Query 4
select xmlquery('$p/category/description/text/text()' passing object_value as "p" returning content) from category_a
Result: "SYS.XMLTYPE".
On the other hand, I noticed, from the result of query 1, that the opening tags of elements keyword and bold are encoded as the less than operator "<". This explains why query 3 returns NULL. However, query 4 should display the text content of <text>, which is not the case.
My questions are about
1. How to properly insert the XML data while preserving the tags (especially the opening tag).
2. How to display the data (the text portion of the main Element or of the nested elements).
The problem about question 1 is that it is quite unfeasible to write a unique insert statement because the structure of <description> is recursive. In other words, if the structure of <description> was not recursive, it would be possible to embed the elements using the xmlelement function during the insertion.
In fact, I need to insert the content of <description> from a source table (called category_a) into a target table (+category_b+) automatically .
I filled category_a using the Saxloader utility from an flat XML file that I have generated from a benchmark. The content of <description> is different from one row to another but it is always valid with regards to the XML Schema. The data is properly inserted as witnessed by the "select * from category_a" instruction (500 row inserted). Besides, the opening tags of the nested elements under <description> are preserved (no "<"). Then I wrote a PL/SQL procedure in which a cursor extracts the category id and category name into varchar2 variables and description into an XMLtype variable from category_a. When I try to insert the values into a category_b, I get the follwing error:
LSX-00213: only 0 occurrences of particle "text", minimum is 1which tells that the <text> element is absent (actually it is present in the source table).
So, my third question is why are not the tags recognized during the insertion?
Can anyone help please?

Hello,
indded, I was using an old version of Sqlplus* (8.0.60.0.0) because I had a previous installation (oracle 10g XE). Instead, I used the Sqlplus* shipped with the 11g2database (version 11.2.0.1.0). All the queries that I wrote work fine and display the data correctly.
I also used the XMLSERIALIZE function and can now display the description content in SQL Developer.
Thank you very much.
To answer your question Marco, I registered the XML Schema using the following code
declare
doc varchar2(4000) := '<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:complexType name="bold_type" mixed="true">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="bold" type="bold_type"/>
               <xs:element name="keyword" type="keyword_type"/>
               <xs:element name="emph" type="emph_type"/>
          </xs:choice>
     </xs:complexType>
     <xs:complexType name="keyword_type" mixed="true">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="bold" type="bold_type"/>
               <xs:element name="keyword" type="keyword_type"/>
               <xs:element name="emph" type="emph_type"/>
               <xs:element name="plain_text" type="xs:string"/>
          </xs:choice>
     </xs:complexType>
     <xs:complexType name="emph_type" mixed="true">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="bold" type="bold_type"/>
               <xs:element name="keyword" type="keyword_type"/>
               <xs:element name="emph" type="emph_type"/>
          </xs:choice>
     </xs:complexType>
     <xs:complexType name="text_type" mixed="true">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="bold" type="bold_type"/>
               <xs:element name="keyword" type="keyword_type"/>
               <xs:element name="emph" type="emph_type"/>
          </xs:choice>
     </xs:complexType>
     <xs:complexType name="parlist_type">
          <xs:sequence>
               <xs:element name="listitem" minOccurs="0" maxOccurs="unbounded" type="listitem_type"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="listitem_type">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="parlist" type="parlist_type"/>
               <xs:element name="text" type="text_type"/>
          </xs:choice>
     </xs:complexType>
     <xs:element name="category">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="name"/>
                    <xs:element name="description">
                              <xs:complexType>
                                        <xs:choice>
                                                       <xs:element name="text" type="text_type"/>
                                                       <xs:element name="parlist" type="parlist_type"/>
                                        </xs:choice>
                              </xs:complexType>
                    </xs:element>
                                                            </xs:sequence>
                                                            <xs:attribute name="id"/>
                                        </xs:complexType>
                    </xs:element>
</xs:schema>';
begin
dbms_xmlschema.registerSchema('/xmldb/category_auction.xsd', doc,     LOCAL      => FALSE,
        GENTYPES   => FALSE, GENBEAN    => FALSE,   GENTABLES => FALSE,
         FORCE      => FALSE,
         OPTIONS    => DBMS_XMLSCHEMA.REGISTER_BINARYXML,
         OWNER      => USER);
end;then, I created the Category table as follows:
CREATE TABLE category_a of XMLType XMLTYPE store AS BINARY XML
    XMLSCHEMA "xmldb/category_auction.xsd" ELEMENT "category";Now, there still remains a problem of how to insert the "description" content which I serialized as a CLOB data into another table as XML. To this purpose, I wrote a view over the Category_a table as follows:
CREATE OR REPLACE FORCE VIEW "AUCTION_XWH"."CATEGORY_V" ("CATEGORY_ID", "CNAME", "DESCRIPTION") AS
select category_v."CATEGORY_ID",category_v."CNAME",
XMLSerialize(content ( xmlquery('$p/category/description/*' passing object_value as "p" returning content)) as clob) as "DESCRIPTION"
from auction.category_a p,
xmltable ('$a/category' passing p.Object_Value as "a"
columns category_id varchar2(15) path '@id',
          cname varchar2(20) path 'name') category_v;Then, I wrote a procedure to insert data into the Category_xwh table (the source and target tables are slightly different: the common elements are just copied wereas new elements are created in the target table). The code of the procedure is the following:
create or replace PROCEDURE I_CATEGORY AS
v_cname VARCHAR2(30);
v_description clob ;
v_category_id VARCHAR2(15);
cursor mycursor is select category_id, cname, description from category_v;
BEGIN
open mycursor;
loop
/*retrieving the columns*/
fetch mycursor into v_category_id, v_cname, v_description ;
exit when mycursor%notfound;
insert into category_xwh values
(XMlElement("category",
      xmlattributes(v_category_id as "category_id"),
      xmlelement("Hierarchies", xmlelement("ObjHierarchy", xmlelement ("H_Cat"),
                                                           xmlelement ("Rollsup",
                                                                              (xmlelement("all_categories",
                                                                               xmlattributes('allcategories' as "all_category_id")))
    xmlforest (
              v_cname as "cat_name",
              v_description as "description")
end loop;
commit;
close mycursor;
END I_CATEGORY;When I execute the procedure, I get the following error:
LSX-00201: contents of "description" should be elements onlyso, I just wonder if this is because v_description is considered as plain text and not as XML text, even if its content is XML. Do I need to use a special function to cast the CLOB as XML?
Thanks for your help.
Doulkifli

Mapping with xml-schema XML-data to relational tables

Hello,
is it possible to map data from xml documents to relational tables with xml-schema?
I mean not in nested tables but in relational tables with primary and foreign keys!
With SQL Server 2005 it is very easy, I dont believe that Oracle couldn't do this!
I searched but i cant find anything about that!
Thx
user445232

indeed, oracle does this for xml schema based xmltype data, however, these underlying tables are not accessable to the application. Maybe It should for next version, so folks who like to use relational model can use it without mapping it manually.
Actually, nested tables, are the same, their underlying tables (segments) are indeed relational tables, oracle manages them internally and not visiable to the application. You can find them in the user_segments, user_objects views though.

TRANSFORM DATA TO XML SCHEMAS

Similar Messages

Maybe you are looking for