XML-Schema IN XML-Document OUT

I have to develop a application that have a XML-Schema as INPUT an a XML-Document as OUTPUT. The Application must select the data from 4 SQL Tables, the selects should be dynamicly created at run time (depending at the struckters in the XML-Schema).
I don't have any know how in XML-DB. Can you help me please.

Covered in the standard demo
See the use of the SQL/XML functions to create an XML view over relational data.
Please also note the following useful examples
XML DB basic Demo at
http://otn.oracle.com/tech/xml/xmldb/demonstrations/xdbBasicDemo.zip
and the instructions at

Similar Messages

XML Schema Validation Partial Document

Is it possible to validate part of a document using Java / XML Schema? I am currently using Xerces 2 / JDOM, but am open to other APIs.
For the example below, I would like to use schema_a to validate that <OtherStuff> has children <Name> and <Address> if <Product> is A.
But, I would like to use schema_b if <Product> is B to validate that <OtherStuff> has children <Name> and <AcctNumber>.
<File>
<Transaction>
     <Product>A</Product>
     <OtherStuff>
         <Name>Me</Name>
         <Address>123 My St.</Address>
     </OtherStuff>
</Transaction>
<Transaction>
     <Product>B</Product>
     <OtherStuff>
         <Name>Me</Name>
         <AcctNumber>123345</AcctNumber>
     </OtherStuff>
</Transaction>
</File>Thanks.

A better approach would be to redesign your element names so that they have fixed meanings, not context-dependent meanings.

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

Invalid or no XML schema in XML Forms Builder

Hi all
Could anyone help me with this?
When I try to preview an Forms example in XML Forms builder I've got the following error:
"Messages or errors reported while building the project Invalid or no XML schema information Error was: Invalid or no XML schema information "
Running EP6 SP2, JRE 1.4.2_05, IE 6.0
Thanks in advance
Mikael Lofberg

Hi Mikael,
If you have not already try saving and rebuilding the project? When you rebuild do you get errors in the project check tab?
If so this should point to the cause of the problem.
Regards
Daniel

XML Document from XML Schema Bug

When an XML document is generated from an XML Schema the XML document does not have all the elements specified in the XML Schema. The XML document only has the root element.
1. Register an XML Schema.
2. Create an XML document with File>New>General>XML>XML Document from XML Schema. The "Generate only Required Elements" is unchecked.
3. The XML document has only the root element.
In JDeveloper 10.1.3 all the elements in the XML Schema get generated.

Also, the component palette for the XML document generated from the XML Schema does not list all the elements in the XML Schema, only the root element is listed. Even if elements are specified as required in the XML Schema with minOccurs="1" and the "Generate only Required Elements" checkbox is selected only the root element gets generated.

How to validate generated XML-Document in Memory by XML-Schema?

Hi all!
I have the following problem:
I am generating a Document using the DOM delivered with Xerces 2.6.2.
Before I'll send the generated xml-document through network to another system I have to check with my xml-schema if the document is correct.
In the DOM-FAQ I found an "example" trying to explain how it should work. But with this example the problems begin.
I am creating my document with this method:
     public void createDocument() {
          myDOM = DOMImplementationImpl.getDOMImplementation();
          doc = myDOM.createDocument("", "documentData", null);
          root = doc.getDocumentElement();
          root.setAttribute(
               "xmlns:xsi",
               "http://www.w3.org/2001/XMLSchema-instance");
          //          root.setAttribute("xsi:noNamespaceSchemaLocation", "myScheme.xsd");
          domConfig = ((DocumentImpl) doc).getDomConfig();
          domConfig.setParameter(
               "schema-location",
               "file:///d:/workspace/XMLProject/WebContent/WEB-INF/myScheme.xsd");
          domConfig.setParameter("error-handler", new EHandler());
          domConfig.setParameter("validate", Boolean.TRUE);
     }In the line getting the domConfig, it is getting differeing to the example: The example is like this:
import org.w3c.dom.Document;
import org.w3c.dom.DOMConfiguration;
import org.w3c.dom.ls.LSParser;
Document document = builder.parseURI("data/personal-schema.xml");
DOMConfiguration config = document.getConfig();
config.setParameter("error-handler",new MyErrorHandler());
config.setParameter("validate", Boolean.TRUE);
document.normalizeDocument();They get the DOM-Configuration from the document-Object, but my document-Object has no "getConfig()" and only after type-casting I get a getDomConfig()-Method to get the configuration.
Then I fill my document and call
((DocumentImpl) doc).normalizeDocument();When I run my Application I get the following error:
org.w3c.dom.DOMException: FEATURE_NOT_SUPPORTED: The parameter schema-location is recognized but the requested value cannot be set.
     at org.apache.xerces.dom.DOMConfigurationImpl.setParameter(Unknown Source)
     at xmlProject.createDocument(Convert.java:63)
     at xmlProject.Convert.main(Convert.java:154)I tried several ways to get the validation without success.
The next question is how I should refer to my xml-schema (which path) and where to place it relative to my jar I will generate, because I will have no webserver I could place it on.
Has anyone any experience with validating a document created and not placed on disc?
I have also another question to SAX: I read, that it is reading a document without saving it in the memory. I think this means that if I am validating it by SAX it will be read once and for parsing it will be read a second time. If I would transfer the document over an tcp-connection, I only have the document once in my inputstream and after validation it would be consumed I think. But what can I parse then? Or did I missed a detail with the function of the SAX?
Thank you for your help!
Yours
Christian

static final String schemaSource = argv[0];
static final String JAXP_SCHEMA_SOURCE =
"http://java.sun.com/xml/jaxp/properties/schemaSource";
DocumentBuilderFactory factory =
DocumentBuilderFactory.newInstance();
factory.setAttribute(JAXP_SCHEMA_SOURCE,
new File(schemaSource));

XML Schema validator fails to load XML Schema from URL

I'm trying to validate an XML document against a set of XML Schemas and the parser seems to freak out: even though all the schemas are referred to in the XML and are properly recognized by Schemas field in XML document properties, I get warnings (multiple
instances):
Request for the permission of type 'System.Net.WebPermission, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed
Cannot resolve the 'schemaLocation' attribute
The schema referenced from this location in your document contains errors
The warning locations are also seemingly random - errors in schema locations are reported on closing tags inside XML or on whitespaces, and so on.
The first warning (System.Net.WebPermission) suggests it has something to do with access to remote schemas, but all the necessary remote schemas are visible in XML Schema Set editor for the document. I also enabled downloading of XML schemas in XML text
editor options.

Hi Tomasz,
Thank you for posting in MSDN forum.
Since this issue is related to the XML Schemas, so we will move this case to the XML forum:https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=xmlandnetfx
, you will get better support.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

XML Schema Collection (SQL Server 2012): Complex Schema Collection with Attribute - Should xs or xsd be used in the coding?

Hi all,
I just got a copy of the book "Pro SQL Server 2008 XML" written by Michael Coles (published by Apress) and try to learn the XML Schema Collection in my SQL Server 2012 Management Studio (SSMS2012). I studied Chapter 4 XML Collection of the book
and executed the following code of Listing 4-8 Complex Schema with Attribute:
-- Pro SQL Server 2008 XML by Michael Coles (Apress)
-- Listing04-08.sql Complex XML Schema with Attribute
-- shcColes04-08.sql saved in C:\\Documents\XML_SQL_Server2008_code_Coles_Apress
-- 6 April 2015 8:00 PM
CREATE XML SCHEMA COLLECTION dbo.ComplexTestSchemaCollection_attribute
AS
N'<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="item">
<xs:complexType>
<xs:sequence>
<xs:element name="name" />
<xs:element name="color" />
<xs:group ref="id-price" />
<xs:group ref="size-group" />
</xs:sequence>
<xs:attribute name="id" />
<xs:attribute name="number" />
</xs:complexType>
</xs:element>
<xs:group name="id-price">
<xs:choice>
<xs:element name="list-price" />
<xs:element name="standard-cost" />
</xs:choice>
</xs:group>
<xs:group name="size-group">
<xs:sequence>
<xs:element name="size" />
<xs:element name="unit-of-measure" />
</xs:sequence>
</xs:group>
</xs:schema>';
GO
DECLARE @x XML (dbo.ComplexTestSchemaCollection_attribute);
SET @x = N'<?xml version="1.0"?>
<item id="749" number="BK-R93R-62">
<name>Road-150 Red, 62</name>
<color>Red</color>
<list-price>3578.27</list-price>
<size>62</size>
<unit-of-measure>CM</unit-of-measure>
</item>';
SELECT @x;
GO
DROP XML SCHEMA COLLECTION dbo.ComplexTestSchemaCollection_attribute;
It worked nicely. But, I just found out the coding that was downloaded from the website of Apress and I just executed was different from the coding of Listing 4-8 listed in the book: all the <xs: ....> and </xs: ..> in my SSMS2012 are
listed as <xsd:...> and </xsd:...> respectively in the book!!?? The same thing happens in the Listing 4-3 Simple XML Schema, Listing 4-5 XML Schema and Valid XML Document with Comple Type Definition, Listion 4-6 XML Schema and XML
Document Document with Complex Type Using <sequence> and <choice>, and Listing 4-7 Complex XML Schema and XML Document with Model Group Definition (I executed last week) too. I wonder: should xs or xsd be used in the XML
Schema Collection of SSMS2012? Please kindly help, clarify this matter and explain the diffirence of using xs and xsd for me.
Thanks in advance,
Scott Chang

Hi Scott,
Using xs or xsd depends on how you declare the namespace prefix.
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="item">
I've posted a very good link in your last question, just in case you might have missed it, please see the below link.
Understanding XML Namespaces
In an XML document we use a namespace prefix to qualify the local names of both elements and attributes . A prefix is really just an abbreviation for the namespace identifier (URI), which is typically quite long. The prefix is first mapped to a namespace
identifier through a namespace declaration. The syntax for a namespace declaration is:
xmlns:<prefix>='<namespace identifier>'
If you have any question, feel free to let me know.
Eric Zhang
TechNet Community Support

Switching ON validate xml(Schema Validation) in BPEL Console for AIAtesting

While we were testing Oracle O2B pip, we have recently switched on schema validation by turning it on to 'Strict' so that we can Validate
XML in BPEL Console. Earlier when we were testing we had turned the schema validation as 'None' on BPEL console, and hence everything was working fine and
no errors we popping out while creating sales order in Siebel CRM. But the moment we put validate xml to ' Strict' it starts throwing validation errors.
So can you please help us to know whether it is right to test the Oracle O2B pip by putting validate xml to 'Strict'? If it is fair to test it by switching
ON Validate XML(putting validate xml to 'Strict') then we are getting below error.
We are creating a new sales order in Siebel CRM and when we check in BPEL console it was faulted at UpdateSalesOrderSiebelCommsProvABCSImpl (v. 1.0) .When we checked the BPEL flow it is throwing error at InvokeUpdateUpsert.
Error is According to the xml schemas, the xml document is invalid. The reason is: Error::cvc-complex-type.2.4.a: Invalid content was found starting with element 'xsdLocal1:Process_spcInstance_spcId'. One of '{"http://siebel.com/asi":Process_spcInstance_spcId}' is expected.
Steps for Switching on Validation ?
1)     Login to BPEL Console
2)     Go To Configuration section
3)     Schema Validation changes
a.     ON: populate validateXML with value strict
b.     OFF: populate validateXML with value none
Really appreciate if you can help..

hi
Indeed, the "Validate XML" menu option only shows "Validate XML: 0 errors, 0 warnings.".
But, if you look at the "Design" tab for your schema, the "invoices" element node contains an "xsd:invoice" sequence shown in red. If you change "xsd:invoice" to "invoice" this becomes white and the node can be expanded.
One other thing, registering an XML Schema in JDeveloper like the one you posted, isn't possible without an "oracle.xml.parser.schema.XSDException" (without further details).
regards
Jan Vervecken

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?

Pulling validation pattern from XML schema in LCD

Hi team,
We have deisgned a fillable PDF form uding Live Cycle Designer ES2.
The form contains fields of different data types.
We have created a data connection on the form (using LCD) to bind it to a XML Schema
The XML schema has different types of validations for different data types.
When we treid to bind the XML schema to PDF form using LCD, most of the validations were pulled in. Example, numeric lenghth check, string length check, minoccurs , maxoccurs
But few validations were not pulled from Schema like Pattern validations on string.
Please guide us on how to achieve this using LiveCycle Designer ES2.
Cheers,
Kavi

Hi Kavi,
The pattern from the XML Schema can not be automatically copied across, I assume because of the differences in the XML Schema pattern regex and a JavaScript regex. If you did use a compatible subset I you could write a macro to add the pattern to the validation event. One difference is a XML Schema pattern always assumes a ^ and $ to match the beginning and end. Have you seen this document http://partners.adobe.com/public/developer/en/livecycle/lc_designer_XML_schemas.pdf,
Regards
Bruce

Validation of XML-Schema

I have a question, if in the XDK there is a
possibility to check a .xsd file, if it belongs to the XML Schema Definition http://www.w3.org/2000/10/XMLSchema
Thanks for your help
Greetings, Merry Christmas and Happy new Year
Andreas

Simply use the self-same XML Schema Processor to validate your *.xsd schema against the schema for XML Schema itself. That is, the XML Schema spec "ships" with a normative XML Schema which describes the valid elements that a schema author can use to write a schema. If you have a particular XML schema definition in hand, it is in particular an instance of a document that should be valid by the XML schema for XML Schema, if you've done it correctly.

Loading Oracle Schema into XML Schema format

Hello,
I'd like to load the Oracle schema information (tables/views, columns, and constraints) into XML Schema format, then read in the XML Schema information to instantiate objects which will be used to build adhoc/dynamic queries. I have the dynamic query part working, but it was not clear to me how to convert the Oracle schema to XML Schema then XML Schema to custom objects. Does anyone have experience with this or ideas as to how to go about this?
Thanks,

Use the Oracle WebRowSet. The WebRowSet interface extends the RowSet interface and is the XML document representation of a RowSet object. A WebRowSet object represents a set of fetched database table rows, including the database metadata, which may be modified without being connected to the database.
http://www.oracle.com/technology/sample_code/tutorials/jdbc10g/webrowset/files/WebRowset.pdf
Refer chapter 10.
http://www.packtpub.com/j2ee-development-with-oracle-jdeveloper-jdbc-4.0/book
Ouput including medata as XML document:
http://www.java2s.com/Code/Java/Database-SQL-JDBC/OutputWebRowSetinXML.htm

What is difference btw schema.core.xml and schema.user.xml in OVD

Hi
New to OVD, I'm looking at Oracle's OVD configuration properties Docoument
I'm confused with list of schema files on OVD especially difference between schema.core.xml and schema.user.xml
In the oracle document it mentioned as below.
Typically, the last file identified is schema.user.xml. Any and all changes to schema are applied to the schema.user.xml file to ensure standard files, such as schema.core.xml, remain unchanged between releases, but can also be virtually modified by having the changes in schema.user.xml override default-shipped schema in schema.core.xml.
If you are installing a manufacturer supplied schema (in DSML form), identify this file in the second to last file in the list of schema files. This will protect the distributed manufacturer file from modification while allowing local customization, which is then stored in schema.user.xml.
Based on above two paragaraphs i came to one understanding but i just want to hear from you what exactly its trying to say about those two files.
Not sure what exactly above mean can someone explain lettle in detail

Hi,
The LDAP schema used by OVD is shipped as several XML files such as schema.core.xml, schema.cosine.xml, schema.inetorperson.xml, schema.nis.xml etc. depending on in which RFC the attribute and object classes are defined.
All changes to these schemas (if any) are always applied to schema.user.xml, so this file contains all the custom attribute types & objetclasses.
Hope this clarifies a bit
Sylvain
When closing a thread as answered remember to mark the correct and helpful posts to make it easier for others to find them

Setting up default toString() in xml schema

I have an xml schema and xml file that contains info for an app I created. Inside of the app, I load the objects into a combo box for the user to select an item. I want the actual objects in the combo box to access the data directly.
Because of the nature of the combo box, it uses toString() for the actual display. In this case I have to modify the impl code to add in a toString() function for this to work correctly, and not give me the name of the object.
Is there away to setup the xsd file to default one the attributes in the xml file to be returned with toString()?
Example:
<xsd:element name="JFeatsList" type="JFeatsType"/>
<xsd:complexType name="JFeatsType">
    <xsd:sequence>
      <xsd:element name="JFeatItem" minOccurs="0" maxOccurs="unbounded">
        <xsd:complexType>
            <xsd:attribute name="FeatName" type="xsd:string"/>
            <xsd:attribute name="FeatType" type="xsd:string"/>
            <xsd:attribute name="Notes" type="xsd:string"/>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
</xsd:complexType>
...I want the FeatName to be sent back with a toString() call.
Thanks,
Mike

I'm an XML newbie myself, so I've probably just finished reinventing some wheels, but in any case, I've written some code that makes reading XML pretty easy.
Here are some useful links:
http://java.sun.com/webservices/docs/1.0/tutorial/index.html
http://java.sun.com/webservices/download.html
http://java.sun.com/webservices/downloads/webservicespack.html
The latter contains C:\jwsdp-1_0_01\samples\jaxp\DOMEcho\DOMEcho.java, which creates a DOM from the XML file, and then traverses the DOM tree. For example, if I want to read the "Company motto" from my XML file: <GUIconstants>
    
    <MOTTO value=""There's a sucker born every minute!""/>
    
    <ComboBox_DatabaseField_Mappings
      combo_0="ORIGIN_COLUMN"
      combo_1="DESTINATION_COLUMN"
      combo_2="CARRIER_COLUMN"
      combo_3="DAY_COLUMN">
    </ComboBox_DatabaseField_Mappings>I have some code like:case Node.ELEMENT_NODE:
category += "." + node.getNodeName();
String temp = category;
if (temp.startsWith(".FBNconfiguration")) {
    temp = temp.substring(".FBNconfiguration".length());
    // FBNconfiguration.GUIconstants
    else if (temp.startsWith(".GUIconstants")) {
      temp = temp.substring(".GUIconstants".length());
      // FBNconfiguration.GUIconstants.MOTTO
      if (temp.equals(".MOTTO"))
        Solitaires.MOTTO = new XMLconversion(node).get(Solitaires.MOTTO);
   * A class to package what's left over
static class Solitaires {
    static String COMMAND_LINE_OPTIONS;
    static int PORT;
    static String WEEKDAYS;
    static int LOCK_DATABASE;
    static int LOCK_LEASE_DURATION;
    static String MOTTO;
    static int SCROLLPANE_JTABLE_WIDTH_DIFFERENCE;
    static boolean BUG_4736093_WORKAROUND;
}XMLconversion is a pretty simple class:package suncertify.fbn.xml;
import org.w3c.dom.*;
* <p>Title: Fly by Night Travels</p>
* <p>Description: Sun Certified Java Developer application</p>
* <p>Copyright: Copyright (c) 2002</p>
* <p>Company: Fly by Night Consultants</p>
* @author Thomas Fly
* @version 1.0
* Convert a single ("Solitaire") XML entry
public class XMLconversion {
String value;
public XMLconversion(Node node) {
    NamedNodeMap atts = node.getAttributes();
    value = atts.item(0).getNodeValue();
public XMLconversion(Node node, boolean concatenate) {
    NamedNodeMap atts = node.getAttributes();
    value = "";
    for (int i = 0; i < atts.getLength(); i++) {
      Node att = atts.item(i);
      value += atts.item(i).getNodeValue() + "\n";
public String get(String dataType) {
    return value;
public int get(int dataType) {
    return new Integer(value).intValue();
public boolean get(boolean dataType) {
    return value.equalsIgnoreCase("true");
}Then in my FBNconstants class, I have stuff like:// GUIconstants
    MOTTO = Solitaires.MOTTO;
    COMBO_CONTENTS = comboBox_DatabaseField_Mappings.COMBO_CONTENTS;By extension, you can read into HashMap's & ArrayList's, and retrieve the translated objects as required.

XML-Schema IN XML-Document OUT

Similar Messages

Maybe you are looking for