Obtain name into name element (XML schema)

Hello abappers,
I need obtain the next code XML schema
<xs:element name='AuditFile'>
    <xs:complexType>
      <xs:sequence>
        <xs:element ref='Header' />
        <xs:element ref='MasterFiles' />
        <xs:element name='GeneralLedgerEntries' />
        <xs:element name='SourceDocuments' />
      </xs:sequence>
    </xs:complexType>
</xs:element>
The code:
l_element_Audito           TYPE REF TO if_ixml_element,
l_document        TYPE REF TO if_ixml_document.
l_element_AuditFile            TYPE REF TO if_ixml_element,
l_element_GeneralLedgerEntries TYPE REF TO if_ixml_element,
l_element_SourceDocuments      TYPE REF TO if_ixml_element,
l_element_Header             TYPE REF TO if_ixml_element,
l_element_MasterFiles             TYPE REF TO if_ixml_element,
Fill root node with value AuditFile
        l_element_AuditFile = l_document->create_simple_element(
                    name = 'AuditFile'
                    parent = l_element_Audito ).
Create element 'Header' as child of 'AuditFile'
        l_element_Header = l_document->create_simple_element(
                    name = 'Header'
                    parent = l_element_AuditFile ).
Create element 'MasterFiles' as child of 'AuditFile'
        l_element_MasterFiles = l_document->create_simple_element(
                    name = 'MasterFiles'
                    parent = l_element_AuditFile ).
Create element 'GeneralLedgerEntries' as child of 'AuditFile'
        l_element_GeneralLedgerEntries = l_document->create_simple_element(
                    name = 'GeneralLedgerEntries'
                    parent = l_element_AuditFile ).
Create element 'SourceDocuments' as child of 'AuditFile'
        l_element_SourceDocuments = l_document->create_simple_element(
                    name = 'SourceDocuments'
                    parent = l_element_AuditFile ).
and with the this code obtain:
<xs:element name="AuditFile">
<xs:complexType>
<xs:sequence>
<xs:element ref="Header" />
<xs:element ref="MasterFiles" />
<xs:element ref="GeneralLedgerEntries" />
<xs:element ref="SourceDocuments" />
</xs:sequence>
</xs:complexType>
</xs:element>
Can you help me, please?
Cordial greetings.

Similar Messages

Extract the job advertisement into a XML-Schema

Hi there,
I have to extraxt the job advertisements in a xml-Schema for making our E-Recruiting compatible to a job-exchange.
Is there a report or tc or something else which extracts the information of the job advertisement in a xml?
Or if not how and where can I read out my Informations about the company or the duration of my job advertisement e.g.
And after I have this information, how can I prepare the information into a dtd (XML-Schema)
Thx for answers

Yes, in fact I solved to do that, now I'm getting a differente problem, I'm trying to get the content to a file, but with no success, I'm getting just "[Document]: #null" into my file, maybe I'm doing something wrong when I try to write it, here's my code in case you or someone else can help me telling me what do I really have to do, thanks in advance.
public class XMLTransformer {
public static void main(String[] args) throws Exception {
try {
String xml_doc = //"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +
//"<!DOCTYPE web-app PUBLIC \"C:\\sms.dtd\">\n" +
"" +
"<root>\n" +
"<sms>\n" +
"<tlf>584123161640</tlf>\n" +
"<op>D</op>\n" +
"<sc>3344</sc>\n" +
"<body>MENSAJE</body>\n" +
"</sms>\n" +
"</root>";
DocumentBuilderFactory factory =
DocumentBuilderFactory.newInstance();
DocumentBuilder builder = factory.newDocumentBuilder();
//Document document = builder.parse(xml_doc);
InputSource inStream = new InputSource();
inStream.setCharacterStream(new StringReader(xml_doc));
Document doc1 = builder.parse(inStream);
File f1 = new File ("c:/salida.xml");
FileWriter out1 = new FileWriter(f1);
PrintWriter wr = new PrintWriter(out1);
f1.createNewFile();
//String inputLine;
//while ((inputLine = lector.readLine()) != null)
wr.write(doc1.toString());
//lector.close();
out1.close(); }

[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.

Specifying Case-Insensitive Element Names in XML Schema

Hope someone knows this!
Is it possible to define an an XML Schema Definition so that Element names in the target XML File can be case insensitive.
At the moment my Parser throws an error if the element names in the XML file do not have the exact same case as the definition in the XML schema.
E.g
In Schema i have:
<xsd:element name="HOSTINVENTORYLINE" type="HostInventoryLineType" maxOccurs="unbounded" minOccurs="0"/>
but in xml file i have
<HostInventoryLine field=""/>
or
<hostinventoryline field=""/>
Does anyone know anyway to get around this, so that the parser accepts the HostInventoryLine element in the xml as an instance of the HOSTINVENTORYLINE element defined in the schema.
Thanks in Advance
JJ
Message was edited by:
[email protected]

You could use substitution groups to handle this. You would need an entry in the schema for each valid capitalization. This won't scale well if you want to be completely case insensitive, but if you only support lower case, upper case, and camel case it should do the trick.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <xs:complexType name="HostInventoryLineType">
          <xs:sequence>
               <xs:element name="an-element" type="xs:string"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="HostInventoryLine" type="HostInventoryLineType"/>
     <xs:element name="HOSTINVENTORYLINE" type="HostInventoryLineType" substitutionGroup="HostInventoryLine"/>
     <xs:element name="hostinventoryline" type="HostInventoryLineType" substitutionGroup="HostInventoryLine"/>
</xs:schema>-Blaise

XML Schema Collection (SQL Server 2012): How to create an XML Schema Collection that can be used to Validate a field name (column title) of an existing dbo Table of a Database in SSMS2012?

Hi all,
I used the following code to create a new Database (ScottChangDB) and a new Table (marvel) in my SQL Server 2012 Management Studio (SSMS2012) successfully:
-- ScottChangDB.sql saved in C://Documents/SQL Server XQuery_MacLochlainns Weblog_code
-- 14 April 2015 09:15 AM
USE master
IF EXISTS
(SELECT 1
FROM sys.databases
WHERE name = 'ScottChangDB')
DROP DATABASE ScottChangDB
GO
CREATE DATABASE ScottChangDB
GO
USE ScottChangDB
CREATE TABLE [dbo].[marvel] (
[avenger_name] [char] (30) NULL, [ID] INT NULL)
INSERT INTO marvel
(avenger_name,ID)
VALUES
('Hulk', 1),
('Iron Man', 2),
('Black Widow', 3),
('Thor', 4),
('Captain America', 5),
('Hawkeye', 6),
('Winter Soldier', 7),
('Iron Patriot', 8);
SELECT avenger_name FROM marvel ORDER BY ID For XML PATH('')
DECLARE @x XML
SELECT @x=(SELECT avenger_name FROM marvel ORDER BY ID FOR XML PATH('Marvel'))--,ROOT('root'))
SELECT
person.value('Marvel[4]', 'varchar(100)') AS NAME
FROM @x.nodes('.') AS Tbl(person)
ORDER BY NAME DESC
--Or if you want the completed element
SELECT @x.query('/Marvel[4]/avenger_name')
DROP TABLE [marvel]
Now I am trying to create my first XML Schema Collection to do the Validation on the Field Name (Column Title) of the "marvel" Table. I have studied Chapter 4 XML SCHEMA COLLECTIONS of the book "Pro SQL Server 2008 XML" written by
Michael Coles (published by Apress) and some beginning pages of XQuery Language Reference, SQL Server 2012 Books ONline (published by Microsoft). I mimicked Coles' Listing 04-05 and I wanted to execute the following first-drafted sql in
my SSMS2012:
-- Reference [Scott Chang modified Listing04-05.sql of Pro SQL Server 2008 XML by Michael Coles (Apress)]
-- [shcColes04-05.sql saved in C:\\Documents\XML_SQL_Server2008_code_Coles_Apress]
-- [executed: 2 April 2015 15:04 PM]
-- shcXMLschemaTableValidate1.sql in ScottChangDB of SQL Server 2012 Management Studio (SSMS2012)
-- saved in C:\Documents\XQuery-SQLServer2012
tried to run: 15 April 2015 ??? AM
USE ScottChangDB;
GO
CREATE XML SCHEMA COLLECTION dbo. ComplexTestSchemaCollection_all
AS
N'<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="marvel">
<xsd:complexType>
<xsd:all>
<xsd:element name="avenger_name" />
<xsd:element name="ID" />
</xsd:all>
</xsd:complexType>
</xsd:element>
</xsd:schema>';
GO
DECLARE @x XML (dbo. ComplexTestSchemaCollection_all);
SET @x = N'<?xml version="1.0"?>
<marvel>
<avenger_name>Thor</name>
<ID>4</ID>
</marvel>';
SELECT @x;
GO
DROP XML SCHEMA COLLECTION dbo.ComplexTestSchemaCollection_all;
GO
I feel that drafted sql is very shaky and it needs the SQL Server XML experts to modify to make it work for me. Please kindly help, exam the coding of my shcXMLTableValidate1.sql and modify it to work.
Thanks in advance,
Scott Chang

Hi Scott,
2) Yes, FOR XML PATH clause converts relational data to XML format with a specific structure for the "marvel" Table. Regarding validate all the avenger_names, please see below
sample.
DECLARE @x XML
SELECT @x=(SELECT ID ,avenger_name FROM marvel FOR XML PATH('Marvel'))
SELECT @x
SELECT
n.value('avenger_name[1]','VARCHAR(99)') avenger_name,
n.value('ID[1]','INT') ID
FROM @x.nodes('//Marvel') Tab(n)
WHERE n.value('ID[1]','INT') = 1 -- specify the ID here
--FOR XML PATH('Marvel') --uncommented this line if you want the result as element type
3)i.check the xml schema content
--find xml schema collection
SELECT ss.name,xsc.name collection_name FROM sys.xml_schema_collections xsc JOIN sys.schemas ss ON xsc.schema_id= ss.schema_id
select * from sys.schemas
--check the schema content,use the name,collection_name from the above query
SELECT xml_schema_namespace(N'name',N'collection_name')
3)ii. View can be viewed as virtual table. Use a view to list the XML schema content.
CREATE VIEW XSDContentView
AS
SELECT ss.name,xsc.name collection_name,cat.content
FROM sys.xml_schema_collections xsc JOIN sys.schemas ss ON xsc.schema_id= ss.schema_id
CROSS APPLY(
SELECT xml_schema_namespace(ss.name,xsc.name) AS content
) AS cat
WHERE xsc.name<>'sys'
GO
SELECT * FROM XSDContentView
By the way, it would be appreciated if you can spread your questions into posts. For any question, feel free to let me know.
Eric Zhang
TechNet Community Support

Adding multiple same-name nodes from one xml into another

Hi,
Following on from my question the other day (Adding multiple different nodes from one xmltype into another), I now have a slightly more complex requirement that I cannot work out where to start, assuming that it's something that can reuse some/all of yesterday's work (thanks again, odie_63!). ETA: I'm on 11.2.0.3
So, here's the (slightly amended) xml along with yesterday's solution:
with sample_data as (select xmltype('<root>
                                       <xmlnode>
                                         <subnode1>val1</subnode1>
                                         <subnode2>val2</subnode2>
                                       </xmlnode>
                                       <xmlnode>
                                         <subnode1>val3</subnode1>
                                         <subnode2>val4</subnode2>
                                       </xmlnode>
                                     </root>') xml_to_update,
                            xmltype('<a>
                                       <b>valb</b>
                                       <c>valc</c>
                                       <d>
                                         <d1>vald1</d1>
                                         <d2>vald2</d2>
                                       </d>
                                       <e>vale</e>
                                       <f>valf</f>
                                       <g>
                                         <g1>valg1</g1>
                                         <g2>valg2</g2>
                                       </g>
                                       <h>
                                         <h1>valh1</h1>
                                         <h2>valh2</h2>
                                       </h>
                                       <multinode>
                                         <name>fred</name>
                                         <type>book</type>
                                         <head>1</head>
                                       </multinode>
                                       <multinode>
                                         <name>bob</name>
                                         <type>car</type>
                                         <head>0</head>
                                       </multinode>
                                     </a>') xml_to_extract_from
                      from   dual)
select xmlserialize(document
           xmlquery(
             'copy $d := $old
              modify (
                insert node element extrainfo {
                  $new/a/b
                , $new/a/d
                , $new/a/f
                , $new/a/h
                } as first into $d/root
              return $d'
             passing sd.xml_to_update as "old"
                   , sd.xml_to_extract_from as "new"
             returning content
         indent
from sample_data sd;
That gives me:
<root>
<extrainfo>
    <b>valb</b>
    <d>
      <d1>vald1</d1>
      <d2>vald2</d2>
    </d>
    <f>valf</f>
    <h>
      <h1>valh1</h1>
      <h2>valh2</h2>
    </h>
</extrainfo>
<xmlnode>
    <subnode1>val1</subnode1>
    <subnode2>val2</subnode2>
</xmlnode>
<xmlnode>
    <subnode1>val3</subnode1>
    <subnode2>val4</subnode2>
</xmlnode>
</root>
However, I now need to add in a set of new nodes based on information from the <multinode> nodes, something like:
<root>
<extrainfo>
    <b>valb</b>
    <d>
      <d1>vald1</d1>
      <d2>vald2</d2>
    </d>
    <f>valf</f>
    <h>
      <h1>valh1</h1>
      <h2>valh2</h2>
    </h>
    <newnode>
      <name>fred</name>
      <type>book</type>
    </newnode>
    <newnode>
      <name>bob</name>
      <type>car</type>
    </newnode>
</extrainfo>
<xmlnode>
    <subnode1>val1</subnode1>
    <subnode2>val2</subnode2>
    <type>book</type>
</xmlnode>
<xmlnode>
    <subnode1>val3</subnode1>
    <subnode2>val4</subnode2>
    <type>car</type>
</xmlnode>
</root>
If it's easier, I *think* we would be ok with something like:
<newnode>
<type name="fred">book</type>
<type name="bob">car</type>
</newnode>
The closest I've come is:
with sample_data as (select xmltype('<root>
                                       <xmlnode>
                                         <subnode1>val1</subnode1>
                                         <subnode2>val2</subnode2>
                                       </xmlnode>
                                       <xmlnode>
                                         <subnode1>val3</subnode1>
                                         <subnode2>val4</subnode2>
                                       </xmlnode>
                                     </root>') xml_to_update,
                            xmltype('<a>
                                       <b>valb</b>
                                       <c>valc</c>
                                       <d>
                                         <d1>vald1</d1>
                                         <d2>vald2</d2>
                                       </d>
                                       <e>vale</e>
                                       <f>valf</f>
                                       <g>
                                         <g1>valg1</g1>
                                         <g2>valg2</g2>
                                       </g>
                                       <h>
                                         <h1>valh1</h1>
                                         <h2>valh2</h2>
                                       </h>
                                       <multinode>
                                         <name>fred</name>
                                         <type>book</type>
                                         <head>1</head>
                                       </multinode>
                                       <multinode>
                                         <name>bob</name>
                                         <type>car</type>
                                         <head>0</head>
                                       </multinode>
                                     </a>') xml_to_extract_from
                      from   dual)
select xmlserialize(document
           xmlquery(
             'copy $d := $old
              modify (
                insert node element extrainfo {
                  $new/a/b
                , $new/a/d
                , $new/a/f
                , $new/a/h
                , element newnode {
                                   $new/a/multinode/name
                                   ,$new/a/multinode/type
                } as first into $d/root
              return $d'
             passing sd.xml_to_update as "old"
                   , sd.xml_to_extract_from as "new"
             returning content
         indent
         ) fred
from sample_data sd;
Which produces:
<newnode>
<name>fred</name>
<name>bob</name>
<type>book</type>
<type>car</type>
</newnode>
- obviously not right!
Can anyone provide any hints? I've tried searching for similar examples, but I mustn't be putting in the right search terms or something!

odie_63 wrote:
or, similarly, to get the alternate output :
copy $d := $old
modify (
insert node element extrainfo {
    $new/a/b
, $new/a/d
, $new/a/f
, $new/a/h
, element newnode {
      for $i in $new/a/multinode
      return element type {
        attribute name {data($i/name)}
      , data($i/type)
} as first into $d/root
return $d
So we're going with the second method, but I've discovered that the "$i/name" node is not always present. When that happens, I would like to use a default value (for example, "george"). I promise I've searched and searched, but I'm completely failing to turn up anything that sounds remotely like what I'm after (seriously, I can't believe my google-fu sucks this badly!).
Is there a simple way of doing it? The only thing that I've found that looks vaguely relevant is "declare default namespace...." but I'm not sure that that's the correct thing to use, or if it is, how I'm supposed to reference it when populating the attribute value.

Non-latin elements (=XML tag names) processing

Hello there,
How could I process XML with non-latin tag names? As far as I know, XI itself cannot map or interact with these XML elements nor design these names in IB.
But I have to work with it and what should I do? The only way for me is to write EJB-module for adapters which could remap these names into latin ones using simple mapping table and XSLT.
PS There are no problems with Unicoded content, but BIG deal with naming convention

Just a remark, surprisingly for me I can use non-latinized (russian for example) XSD as an external definition and create message type based on it.
And I can use russian elements in graphical mapping too but not in own XI elements.
So this is much more interface problem, not basis one.

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?

Insert XHTML elements inside XML schema

Hi,
My oracle version is 10.2.0.2.0. Following this suggest :
http://forums.oracle.com/forums/thread.jspa?messageID=835251&#835251
I tried to create a schema in this way:
<?xml version="1.0"?>
<xs:schema
     xmlns:xs="http://www.w3.org/2001/XMLSchema"
     xmlns:xdb="http://xmlns.oracle.com/xdb"
     targetNamespace="http://test.example.it/test"
     xmlns="http://test.example.it/test"
     elementFormDefault="qualified"
     attributeFormDefault="unqualified">
     
     <xs:element name="Project">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="AnnoBando" type="xs:string" xdb:SQLType="CLOB"/>
                    <xs:element name="AnnoBando2" type="xs:string"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
</xs:schema>In this schema only element "AnnoBando" contains XHTML elements, my question is, when I upload my xml document, can I pass directly XHTML elements in this way?
insert into TESTSQLTYPE values ('codice', xmltype('
<Project
     xmlns = "http://test.example.it/test"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xmlns:xml="http://www.w3.org/XML/1998/namespace"
     xsi:schemaLocation = "http://test.example.it/test http://test.example.it/test2.xsd">
     <AnnoBando> text <b>bolded text</b> text</AnnoBando>
<AnnoBando2>empty text</AnnoBando2>
</Project>
'))or I should insert html entities of "<" and ">" of the element?
If i try to insert the xml example specified here I get this error:
ORA-31187: Cannot Add Node 'b' (type='element') to Simple Type Node '/Project/Annobando'Thanks for your help.
Stefano

Try these two:
1.
======
<AnnoBando>![CDATA[text <b>bolded text</b> text]]</AnnoBando>
=======
2.
======
<AnnoBando> text &lt;b&gt;bolded text&lt;/b&gt; text</AnnoBando>
=======<p>
Basically, because '<' and '>' are used for element declarations in XML, you cannot include them 'nude' in the element content. The above are two methods of escaping those characters.
<p>
Leigh.

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;

Add file name to the element in target message

Hi all!
I try to configure scenario:
Get all files from directory (it will not be the same number of file every time) and mapping this file to the ERP system. I use File adapter to do this. But what Is necessary I need to mapp the file name to the element in target message.
I mean: When I have got the RFC structure imprted from ERP and there I have got the element "filename". I would like to put the file name of file which I mapping to this element. Next put the all file contents with file name to the ERP table.
It is possible to do that??
I found in sap help that I can keep file name in the message header to get the same target file name, but I wont to put file contents (with file name) to the ERP table not to another file.
THX for all your opinions.

The DynamicConfiguration fin inbound message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:DynamicConfiguration xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="Directory">/usr/sap/PXD/put/archive</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="FileEncoding">ISO646-US</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="SourceFileTimestamp">20061212T121622Z</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="FileType">txt</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="FileName">200610.TXT</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="SourceFileSize">124</SAP:Record>
</SAP:DynamicConfiguration>
and for Response:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:DynamicConfiguration xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="SourceFileSize">124</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="FileType">txt</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="SourceFileTimestamp">20061212T121622Z</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="FileEncoding">ISO646-US</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="FileName">200610.TXT</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="Directory">/usr/sap/PXD/put/archive</SAP:Record>
</SAP:DynamicConfiguration>

Script to insert file name into keywords field of same file

Hello,
search a solution, a Script or another, which writes the file name into keywords field of same file (Metadata: Description/Keywords) in "photoshop", "bridge" or better in "Lightroom" .
I found this topic from Mike Hale http://www.ps-scripts.com/bb/viewtopic.php?t=1330
It's possible this script to change this in such a way that it does this:
"script to insert file name into keywords field of same file"
Thanks and best greetings
Wolfgang

This works in CS2:-
#target bridge
   if( BridgeTalk.appName == "bridge" ) {
nameDescription = MenuElement.create("command", "AddName to Description", "at the beginning of Thumbnail");
nameDescription .onSelect = function () {
     nameToDescription();
function nameToDescription(){
var items = app.document.selections;
      for (var i = 0; i < items.length; ++i) {
         var item = items[i];
var m = item.synchronousMetadata;
filenameToDesc(m, item.name.slice(0,-4));
function filenameToDesc(metadata, Description) {
var strTmpl = "name2Desc";
var strUser = Folder.userData.absoluteURI;
var filTmpl = new File(strUser + "/Adobe/XMP/Metadata Templates/" + strTmpl + ".xmp");
var fResult = false;
try
{ if (filTmpl.exists)
filTmpl.remove();
fResult = filTmpl.open("w");
if (fResult) {
filTmpl.writeln("<x:xmpmeta xmlns:x=\"adobe:ns:meta/\" x:xmptk=\"3.1.2-113\">");
filTmpl.writeln(" <rdf:RDF xmlns:rdf=\"http://www.w3.org/1999/02/22-rdf-syntax-ns#\">");
filTmpl.writeln(" <rdf:Description rdf:about=\"\" xmlns:dc=\"http://purl.org/dc/elements/1.1/\">");
filTmpl.writeln("<dc:description>");
filTmpl.writeln("<rdf:Alt>");
filTmpl.writeln("<rdf:li xml:lang=\"x-default\">"+Description+"</rdf:li>");
filTmpl.writeln("</rdf:Alt>");
filTmpl.writeln("</dc:description>");
filTmpl.writeln(" </rdf:Description>");
filTmpl.writeln(" </rdf:RDF>");
filTmpl.writeln("</x:xmpmeta>");
fResult = filTmpl.close();
metadata.applyMetadataTemplate(strTmpl, "replace");
filTmpl.remove();
catch(e)
{ fResult = false; }
return fResult;

Question about xml schemas and the use of unqualified nested elements

Hello,
I have the following schema:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns="http://xml.netbeans.org/examples/targetNS"
    targetNamespace="http://xml.netbeans.org/examples/targetNS"
    elementFormDefault="unqualified">
    <xsd:element name="name" type="xsd:string"/>
    <xsd:element name="age" type="xsd:int"/>
    <xsd:element name="person">
        <xsd:complexType>
            <xsd:sequence>
                <xsd:element ref="name"/>
                <xsd:element ref="age"/>
               <xsd:element name="height" type="xsd:int"/>
            </xsd:sequence>
        </xsd:complexType>
    </xsd:element>
</xsd:schema>I am just wondering why would someone have a nested element that is unqualified? here the "height" element.
Can anyone explain this to me please?
Thanks in advance,
Julien.
here is an instance xml document
<?xml version="1.0" encoding="UTF-8"?>
<person xmlns='http://xml.netbeans.org/examples/targetNS'
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xsi:schemaLocation='http://xml.netbeans.org/examples/targetNS file:/E:/dev/java/XML/WebApplicationXML/web/newXMLSchemaThree.xsd'>
<name>toto</name>
<age>40</age>
<height>180</height>
</person>

Don't worry about it.
There are two different styles of schemas. In one style, you define the elements, attributes, etc. at the top, and then use the "ref" form to refer to them. (I call this the "global" style.) The other style is to define elements inline where they are used. ("local" style)
Within some bounds, they work the same and which you use is a choice of you and the tools that generate the schemas.
A warning about the local style. It is possible to define an element in two different locations in the schema that are different. It will get past all schema validation, but it seems wrong to my sense of esthetics. With the global style, this will not happen.
So, how did this happen? Probably one person did the schema when it only had a name and age. Then, someone else added the height element. They either used a different tool, or preferred the other style. I'm aware of no difference in the document you have described between the two styles.
Dave Patterson

XML Schema any element

I have a list of schema files and they a number of elements in them. But for my data extraction i use only close to 300 tags. When i register the schema I get an error that a table cannot of have more than 1000 columns. My work mate is working on Annotations and I am planning to build a new schema to make extract only these 300 tag names and also make sure the XML file can be validated like it did earlier. Explaining this i came across a complex type element called *<any>* which can be used to allow elements to be available which are not declared within the schema file.
My Original schema file looks something like below,
<xsd:complexType name="WfInformation">
<xsd:all minOccurs="0">
<xsd:element name="Company" type="WfCompany" minOccurs="0" />
<xsd:element name="HeadOffice" type="WfOffice" minOccurs="0" />
<xsd:element name="IndependentOffice" type="WfIOffice" minOccurs="0" />
<xsd:element name="AffiliateCompany" type ="WfIAOffice" minOccurs="0" />
<xsd:element name="Number" type="xsd:string" minOccurs="0" />
<xsd:element name="ReferenceID" type="xsd:string" minOccurs="0" />
</xsd:all>
</xsd:complexType>
of the above list of items i use only elements Company, HeadOffice, Number. After reading through some documentation I wanted to <any> tag like below,
<xsd:complexType name="WfInformation">
*<xsd:sequence>*
<xsd:element name="Company" type="WfCompany" minOccurs="0" />
<xsd:element name="HeadOffice" type="WfOffice" minOccurs="0" />
*<xsd:any processContents="lax"/>*
*<xsd:any processContents="lax"/>*
<xsd:element name="Number" type="xsd:string" minOccurs="0" />
*<xsd:any processContents="lax"/>*
*</xsd:sequence>*
</xsd:complexType>
My question is if I am correcting the lines as i mentioned above will be Register schema again fail with same reason that i have 1000 columns. As i understand every element inside an Complex element is stored as a column value. In that case will this redesign work. Or is there any other way to approach re-desgin the XML Schema.

Thanks. I think that leaves out my option to create a totally new Schema to suit my XML files.
Only other option we have is to use Annotations.
I think my colleague - eoin62 would have shared the XML Schema files earlier through your oracle email address.
Please refer thread - How to register multiple XSD files
But we received a reply and we knew very little on how to make changes to Admin.xsd and how would that solve our problem. Please correct me if i am incorrect. Because the biggest Schema was estimate.xsd that has close to 800+ elements. I am not sure if my colleague sent you the necessary tag names we use within the Schema. We have close to around 300 tags we use. But our combined XML Schema has close to 1600+ If we have to annotate, i thought it would be better we tell Oracle which tagswe need, which inturn should should help better create XMLtype table against a Schema and work on performance.
Your earlier reply was,
Basically in XML Schema Admin.xsd element AdminCompin WorkfileTypeneeds to be stored Out of line..
Add the annotations xdb:SQLInline=”false” and xdb:defaultTable=”ADMIN_COMP_XML”. to the element..
if you can share with our XML Schema on how to annotate or if you can share a location that shows how an annotated or non-annotated Schema works that would help us correcting our Schema files.
Thanks for all your support. We have gone a long way in XML Parsing in the last 6 weeks.
Edited by: beta32c on Feb 19, 2013 12:09 AM

Xml Schema xs:choice element in dynamic forms

Hi all,
I'm developing an xml schema for creating the data model of a form. I connect LC Designer-8.2ES to this schema.
In the schema I do have mutually exclusive elements implemented with a <xs:choice> element. A very comparable situation was described in this thread : http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=123 in 2007.
The problem, as related in this thread, is that only the very first element of the choice is displayed in the generated pdf and I don't know how to display all parts as a real choice. So what's the best way to let user fill in one part or the other of the choice?
Does it need to be implemented with scripting (xfa...myform.presence = visible | hidden)?
I want that only the filled element of the choice be exported from the form, the resulting xml being valid according the schema. I seems to work, but as of now, only for the first element...
BTW, what's the best document describing what parts of xml schema are usable in dynamic XFA forms? Is it 100% compatible? I've observed that the constraints in my schema are not validated in the forms. Shouldn't xml schema generate validating script in LCD? Does it apply for a subset of xml schema?
Thanks in advance,
jgrd

Hi all,
finally, I understand that we cannot use "anonymous" sequences neither in LiveCycle (like this following example where person might have many email)
    <xs:element name="person">
        <xs:complexType>
            <xs:sequence maxOccurs="unbounded">
                <xs:element name="email" type="xs:string"/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>
valid instance with 3 emails :
<person xsi:noNamespaceSchemaLocation="Untitled39.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <email>String</email>
    <email>String</email>
    <email>String</email>
</person>
In LC Designer, element with same name (<email>) are not used AFAK. Maybe I'm wrong?
The same hands with <xs:choice> where only first choice appears in pdf although being present in LC Designer.
As for sequences, my idea is to produce <email1>, <email2>, etc. in a static schema, before connecting schema's data to LCD.
Hope someone can show up and tell it's the right way or not.
Regards
jgrd

Obtain name into name element (XML schema)

Similar Messages

Maybe you are looking for