XML Schema include problem

Hello,
Designer 7.1 crashes while loading xsd schema with xsd:include
I've tried with absolute path:
and relative path:
and results are the same: no message, the only thing to do is to kill Designer
I am working with 7.1 french version
Can somebody help me
Maciek Dambski

Your schemaLocation value is not a URI? To me, it looks like the value should conform to this:
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#anyURI
I will let you read all those specs to see whether that is your problem.

Similar Messages

Xml schema validation problem

Hi All
How to tackle this xml schema validation problem
i am using the sample code provided by ORacle technet for xml
schema validation in the Oracle database(817).
The sample code works perfectly fine.
Sample as provided by http://otn.oracle.com/tech/xml/xdk_sample/archive/xdksample_093001.zip.
It works fine for normal xml files validated against
xml schema (xsd)
but in this case my validation is failing . Can you let me know why
I have this main schema
Comany.xsd
===========
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.company.org"
xmlns="http://www.company.org"
elementFormDefault="qualified">
<xsd:include schemaLocation="Person.xsd"/>
<xsd:include schemaLocation="Product.xsd"/>
<xsd:element name="Company">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Person" type="PersonType" maxOccurs="unbounded"/>
<xsd:element name="Product" type="ProductType" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
================
which includes the following 2 schemas
Product.xsd
============
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xsd:complexType name="ProductType">
<xsd:sequence>
<xsd:element name="Type" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
==============
Person.xsd
===========
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xsd:complexType name="PersonType">
<xsd:sequence>
<xsd:element name="Name" type="xsd:string"/>
<xsd:element name="SSN" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
=================
now when i try to validate a xml file against Company.xsd
it throws an error saying unable to find Person.xsd.
no protocol error
Now where do i place these 2 schemas(.xsd files) Person & product
so that the java schemavalidation program running inside Oracle
database can locate these files
Rgrds
Sushant

Hi Jinyu
This is the java code loaded in the database using loadjava called by a wrapper oracle stored procedure
import oracle.xml.parser.schema.*;
import oracle.xml.parser.v2.*;
import java.net.*;
import java.io.*;
import org.w3c.dom.*;
import java.util.*;
import oracle.sql.CHAR;
import java.sql.SQLException;
public class SchemaUtil
public static String validation(CHAR xml, CHAR xsd)
throws Exception
//Build Schema Object
XSDBuilder builder = new XSDBuilder();
byte [] docbytes = xsd.getBytes();
ByteArrayInputStream in = new ByteArrayInputStream(docbytes);
XMLSchema schemadoc = (XMLSchema)builder.build(in,null);
//Parse the input XML document with Schema Validation
docbytes = xml.getBytes();
in = new ByteArrayInputStream(docbytes);
DOMParser dp = new DOMParser();
// Set Schema Object for Validation
dp.setXMLSchema(schemadoc);
dp.setValidationMode(XMLParser.SCHEMA_VALIDATION);
dp.setPreserveWhitespace (true);
StringWriter sw = new StringWriter();
dp.setErrorStream (new PrintWriter(sw));
try
dp.parse (in);
sw.write("The input XML parsed without errors.\n");
catch (XMLParseException pe)
sw.write("Parser Exception: " + pe.getMessage());
catch (Exception e)
sw.write("NonParserException: " + e.getMessage());
return sw.toString();
This is the code i used initially for validating a xml file against single xml schema (.xsd) file
In the above code could u tell how to specify the second schema validation code for the incoming xml.
say i create another Schemadoc for the 2nd xml schema.
something like this with another parameter(CHAR xsd1) passing to the method
byte [] docbytes1 = xsd1.getBytes();
ByteArrayInputStream in1 = new ByteArrayInputStream(docbytes1);
XMLSchema schemadoc1 = (XMLSchema)builder.build(in1,null);
DOMParser dp = new DOMParser();
How to set for the 2nd xml schema validation in the above code or can i combine 2 xml schemas.
How to go about it
Rgrds
Sushant

Oracle Xml Schema Registration problem.

Hi Gurus,
I tried to register a schema using an xsd named 'EntityBase.xsd', using the following block. It got registered successfully.
BEGIN
DBMS_XMLSCHEMA.registerSchema(
SCHEMAURL => 'http://xmlns.oracle.com/xdb/EntityBase.xsd',
SCHEMADOC => bfilename('XMLDIR','EntityBase.xsd'),
LOCAL => FALSE,
CSID => nls_charset_id('AL32UTF8'));
END;
select local,schema_url,int_objname,qual_schema_url from dba_xml_schemas where schema_url like
'%http://xmlns.oracle.com/xdb/EntityBase.xsd%';
This gives me a record.
Now I have another xsd, VersionedEntity.xsd with which I would like to register another schema. In the xsd definition for VersionedEntity.xsd, it has Entity.xsd being used and which is already registered and the .xsd exists in the same directory 'XMLDIR'. But when I register using the following block,
BEGIN
DBMS_XMLSCHEMA.registerSchema(
SCHEMAURL => 'http://xmlns.oracle.com/xdb/VersionedEntity.xsd',
SCHEMADOC => bfilename('XMLDIR','VersionedEntity.xsd'),
CSID => nls_charset_id('AL32UTF8'));
END;
I get
ORA-31000: Resource 'EntityBase.xsd' is not an XDB schema document
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 37
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 61
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 126
ORA-06512: at line 2
Please help me with your expert advice. Am I doing something wrong?
Thanks and Regards,

There is a forum dedicated to XML...
XML DB

WE60 - Error while generating the xml schema

Hi
Using the transaction WE60 I am trying to generate an XML schema for the BASIC type : DEBMDM06, Segment release - 7 and record type version - 3. Following error message is displayed. "Structure of segment E1T023W is unknown". Kindly let me know how to generate an XML schema successfully and what is the reason for this error to come up
Regards
Aruna

Hi Aruna,
It seems a dictionary error but it doesn't occurs to me. I can download the XML schema without problems in SAP ECC 6.0.
If you let me know your email I can send it zipped to you.
Reward points if helps.
Roger

Problems using mathml XML Schema in XMLDB

I have successfully loaded the hierarchy of XML Schema definition documents for the current 'mathml' by adjusting the relative paths in all include and import statements, and by forcing the load to overcome cyclic dependency issues.
However when I try to create a table using the XMLTYPE or register another schema which is dependent on mathml I receive the following error:
ERROR at line 1:
ORA-31079: unable to resolve reference to group "Content-expr.class"
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 37
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 61
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 126
ORA-06512: at line 14
Having tried loading into both 9iR2 and 10GR2 databases and pasting the document containing the 'Content-expr.class' into the parent document (i.e. removing the include) I have come to the conclusion that there is a problem with the schema definition.
However being new to XML I do not know what ths issue is as the file containing the definition (math.xsd) is included well before the references in the parent document.
Here is the group definition corresponding to the offending reference:
<xs:group name="Content-expr.class">
<xs:choice>
<xs:group ref="ContExpr.class"/>
<xs:group ref="PresExpr.class"/>
</xs:choice>
</xs:group>
I am also unable to trace which reference is causing the problem as there are several.
Does anyone have any suggestions as to what could be causing this issue, or how I can obtain further diagnostics?
Any help much appreciated.
Robert Honeyman
*********** New info ***************
OK. I have tried further to register the schema, and have the following additional information.
I determined that I thought my problem was cyclic dependencies being resolved ONLY by virtue of the parent file mathml2.xsd. I therefore pasted all the files together in include order so that this was no longer an issue. I then performed the following actions:
1. I tried to register into Oracle 9iR2 database (9.2.0.4) and received the following error:
ERROR at line 1:
ORA-31151: Cyclic definition encountered for group: "Content-expr.class"
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 0
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 26
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 131
ORA-06512: at line 14
2. I then tried registering the schema into an Oracle 10G Release 2 database as well, and received the following error:
ORA-31084: error while creating table "MEDLINE"."math729_TAB" for element
"math"
ORA-01792: maximum number of columns in a table or view is 1000
ORA-02310: exceeded maximum number of allowable columns in table
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 37
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 61
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 126
ORA-06512: at line 14
My conclusions are as follows:
1. 9iR2 (the version I was using at least 9.2.0.4) can't handle cyclic dependencies at all, or at least not complex ones.
2. Neither 9iR2 or 10gR2 can handle cyclic dependencies (or other dependent definitions managed purely by virtue of a parent file with multiple include statements)
3. 10gR2 can handle cyclic dependencies when they are all defined in the same file or resolved by an explicit include regardless of complexity.
4. 10gR2 cannot handle highly complex XML Schema definitions due its limit of 1000 columns per table.
Does anyone have any comments on these conclusions?
I don't even want to handle Mathml, just another schema definition that imports it. I may try to make my own adjustments.
Message was edited by:
rhoneyman
null

Thanks, I found the relevant sections in the XML DB 10GR2 documentation (chapter 3 I think). As far as I can tell my options are to either use one of the following:
- top-down technique creating tables for sub elements in the schema definition
- bottom-up technique collapsing some of the lower elements into CLOBs (I guess this is semi-structured storage)
The problem with Mathml is that it seems quite complex, with only one global schema element and many nested elements, hence only one table is created by XMLDB and it logically follows that we run out of columns.
To get it to work is likely to involve a fair amount of manual schema modification, which incurs a maintenance overhead for me.
It would be good if Oracle could provide a way of simplifying this maintenance of complex schemas to get them to be registered. I guess this would be increasing the number of columns alllowed for a table or offering some other parametric option for DBMS_XMLSCHEMA.REGISTER_SCHEMA that allowed a threshold and either a top-down or bottom-up approach to be taken automatically.
For the time being I am using a simplified schema that does not depend on Mathml for my storage needs.

JSTL - Problem parsing XML file w/ XML schema declarations

I'm having trouble parsing an xml document that contains XML schema declarations in the root element. I've included 2 snippets, the XML files they're supposed to parse, and their output below. The first one works and the second one doesn't. Could someone please tell me why? I find it hard to believe that no one's run into this before.
I'm running Tomcat 5.5 and I'm using JSP 2.0, jakarta standard taglibs jars (1.1.2), jdk 1.5.0_04, and the Xalan 2.7.0 jars.
Here's the first snippet:
<c:import url="/WEB-INF/config/schools.xml" var="xml" />
<x:parse doc="${xml}" var="schoolList"/>
There are <x:out select="count($schoolList//school)"/> schools in the file:<br/>
<x:forEach select="$schoolList//school">
     <x:out select="name"/><br/>
</x:forEach>it parses the following xml file:
<?xml version="1.0" encoding="UTF-8"?>
<schools>
     <school id="34033">
          <name>Tumwater Middle School</name>
          <district>Tumwater</district>
          <type>middle</type>
          <active>false</active>
     </school>
     <school id="17001">
          <name>Garfield High School</name>
          <district>Seattle</district>
          <type>high</type>
          <active>true</active>
     </school>
     <school id="00023">
          <name>Tigard High School</name>
          <district>Tigard-Tualatin</district>
          <type>high</type>
          <active>true</active>
     </school>
</schools>and it outputs:
There are 3 schools in the file:
Tumwater Middle School
Garfield High School
Tigard High School-----------------------------------------
The second snippet:
<c:import url="/WEB-INF/config/schools2.xml" var="xml2" />
<x:parse doc="${xml2}" var="schoolList2"/>
There are <x:out select="count($schoolList2//school)"/> schools in the file:<br/>
<x:forEach select="$schoolList2//school">
     <x:out select="name"/><br/>
</x:forEach>parses this xml file (note the xml schema declarations):
<?xml version="1.0" encoding="UTF-8"?>
<schools xmlns="http://www.serenus.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.serenus.com schools.xsd">
     <school id="34033">
          <name>Tumwater Middle School</name>
          <district>Tumwater</district>
          <type>middle</type>
          <active>false</active>
     </school>
     <school id="17001">
          <name>Garfield High School</name>
          <district>Seattle</district>
          <type>high</type>
          <active>true</active>
     </school>
     <school id="00023">
          <name>Tigard High School</name>
          <district>Tigard-Tualatin</district>
          <type>high</type>
          <active>true</active>
     </school>
</schools>and its output is:
There are 0 schools in the file:That's it! No errors at all! I'm 100% certain the variable names, filenames, etc. are correct. I've looked everywhere for an existing answer to this problem, but I can't find one. Is this a known issue? Please help.
-Ben

Hi Ben,
I got exactly the same problem and also could not find any solution.
Did you find a way out for this problem meanwhile?
Any help is welcome!

Problem with running sample code from XML Schema Processor for Java

Hi there,
I downloaded the XML Schema Processor for Java and tried it out. Unfortunately, it failed at the first step. FYI, I included all xmlparserv2.jar and xmlschema.jar in my classpath.
I compiled XSDSample.java with a warning: XSDSample.java uses a deprecated API. Recompile with "-deprecation" for details. There was no problem with compiling XSDSetSchema.java.
When I tried to run report.xml by typing java XSDSample report.xml, I got Parsing report.xml
NonParserException: null.
I guess that report.xml from the sample is not valid.
Could any one give me a hint? Any suggestion would be greatly appreciated.
---Denali
null

Please post this message at:
Forums Home » Oracle Technology Network (OTN) » Products » Database » XML DB

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?

Problem in parsing XML Schema

I am trying to parse XML Schema using XSOM. The Schema has <xs:include>s
e.g. I have first.xsd which includes second.xsd and second.xsd again includes third.xsd.
First.xsd
<xs:include schemaLocation="../Second.xsd">....
Second.xsd
<xs:include schemaLocation="Third.xsd">....
When I parse "First.xsd" parser passes the correct path "C:/XSDSchema/Second.xsd"(First.xsd resides in "C:/XSDSchema/Schema/") to the EntityResolver's resolveEntity method. But for Second.xsd it passes "Third.xsd" only (Third.xsd resides in "C:/XSDSchema/" ) .
Any Idea ?????

Here is a screenshort of the part of my workflow:
In the mappings of the "Set Value" activity, I have one line with those properties:
Location: /process_data/bonusValidationForm/object/data/xdp/datasets/data/BonusValidationForm/buMan agerID
Expression: /process_data/currentUser/object/@userId
Where:
bonusValidationForm is a process variable of my workflow that point my xdp form
buManagerID is the textfield I want to set
currentUser is a process variable (type User) that was well setted by the task Find BU Manager

Facing problem in xml schema xsd file registration

Hi,
i am facing problem in xml schema xsd file registration when
the number of column is more. It is showing persing error.
if i am deleting few column from xsd file . It is working otherwise
showing error. Is there any solution for that please suggest me.
The Error is
ORA-31011:XML parsing failed
ORA_19202: Error occurred in XML processing
LPX-00230 : (message vary time to time-like invalid tag ending etc.)
Regards
Manoranjan
and thanks in advance

Where is you XML coming from. Are you sure it's valid. If you are hard coding it as a SQL String constant are you hitting the 4k / 32K limit on the size of SQL / PL/SQL constant. Have you tried loading the content from a bfile..

Problem inserting and querying XML data with a recursive XML schema

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

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

Using xml schema problem (SAP MDM 7.1 Syndicator)

Good day !
I try to syndicate directory which correspond to some xml-schema and I have a problem.
I want to syndicate data from hierarchy table which have one field which have a type like lookup <Flat> (multivalued).
In XML-schema element "DEF_PRODUCT" and "DEF_PRODUCT_CODE" - attribute presents hierarchy table.
"CREDIT_PRODUCT" and childs presents linked flat table.
According idea and business rules I must get the result like this: each "DEF_PRODUCT" have N-"CREDIT_PRODUCT". One - to- many.
But when I set up all map completely and look to xml result file I start to be disappointed.
XML result file approximately must be like this:
<DEF_PRODUCT>
    <CREDIT_PRODUCT/>
    <CREDIT_PRODUCT/>
    <CREDIT_PRODUCT/>
</DEF_PRODUCT>
but in result I have all <CREDIT_PRODUCT> in one node and child attributes.
I attach 3 pics which explain my situation.
xml-schema :[http://xmages.net/storage/10/1/0/6/3/upload/42ca6ca8.jpg]
field mapping: [http://xmages.net/storage/10/1/0/6/a/upload/bbbc09f2.jpg]
example: [http://xmages.net/storage/10/1/0/c/c/upload/817b0e23.jpg]
Anybody can help me?
About software : SAP MDM 7.1 (7.1.04.139)
P.S: My problem can be resolved succesfully if I will use 1 <main> table and 1 <qualified flat> table.
       But in my case I must use hierarchy - structure because it most usable for business - users

>
Christian Heuer wrote:
> Hi,
>
> now I understood and you really have got a point here. But the question is whether you need key mapping then on the remote key level with a tuple anymore. If yes, you won
>
> Best regards
> Christian
If SAP MDM will present many opportunities to me I will be very glad.
I repeat I must get output xml which have the pair like "RemoteKey"="RemoteSystem" in tuple subnode.
In tuple, after your advices.
Ideally, Syndicator must present to each user ability to choose pair "RemoteKey" = "RemoteSystem" in each subnode like <LookUp> table in root (look at my example pic).
Imagine you have one root table and N-linked <lookup> tables.
Tree like this :
<main tbl>
<subtbl1/>
<subtbl2/>
<subtbl3>
     <childtbl1/>
     <childtbl2/>
</subtbl3>
</main tbl>
It's dangerous to deprive SAP MDM user to select pair "RemoteKey" = "RemoteSystem" from ROOT to ALL and LAST LEAF in abstract hierarchy. How do you think ?
Now, I haven't abilities to solve my problem using standard resources. Really ?

XML Schema Class Generator Problem compiling generated java programs

Hi,
I ran oracg on the po.xsd schema from X3Cs XML Schema Part 0: Primer which successfully generated the java codes. I ran into problems when I compile the generated classes. Here's what I'm getting:
C:\oracle\xml\xdk\demo\java\classgen\Po2>javac -classpath ".;C:\oracle\xml/lib/xmlparserv2.jar;C:\oracle\xml/lib/xschema.jar;C:\oracle\xml/l
ib/classgen.jar;.;C:\Program Files\VicunaJ521\java\lib\collections.jar;C:\Program Files\VicunaJ521\java\lib\vicunalite.jar;C:\Program Files\
XConverter\XConverter.jar;C:\Program Files\XConverter\IDLGenerator.jar; c:\jdk1.2.2\lib\dt.jar;c:\jdk1.2.2\lib\jvm.jar;c:\jdk1.2.2\lib\tools
.jar;c:\oracle\ora81\jdbc\lib\classes12.zip;c:\oracle\ora81\jdbc\nls_charset12.zip;C:\oracle\xml\lib\classgen.jar;C:\oracle\xml\lib\xmlparse
rv2.jar" *.java
.\types\PurchaseOrderType.java:75: Type expected.
public void addComment(null.Comment thecomment)
^
.\types\Items.java:141: Type expected.
public void addComment(null.Comment thecomment)
^
2 errors
Running the demo which comes with oracles version of po.xsd was OK. What's the difference between the po.xsd from oracle and the po.xsd from W3C? Are there any W3C recommendation for XML Schema not supported by Oracle's class generator?

Which po.xsd do you use? Would you post it?
Thanks. Here's the copy of the po.xsd from the W3C website. (http://www.w3.org/TR/xmlschema-0/#po.xsd)
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Purchase order schema for Example.com.
Copyright 2000 Example.com. All rights reserved.
</xsd:documentation>
</xsd:annotation>
<xsd:element name="purchaseOrder" type="PurchaseOrderType"/>
<xsd:element name="comment" type="xsd:string"/>
<xsd:complexType name="PurchaseOrderType">
<xsd:sequence>
<xsd:element name="shipTo" type="USAddress"/>
<xsd:element name="billTo" type="USAddress"/>
<xsd:element ref="comment" minOccurs="0"/>
<xsd:element name="items" type="Items"/>
</xsd:sequence>
<xsd:attribute name="orderDate" type="xsd:date"/>
</xsd:complexType>
<xsd:complexType name="USAddress">
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="street" type="xsd:string"/>
<xsd:element name="city" type="xsd:string"/>
<xsd:element name="state" type="xsd:string"/>
<xsd:element name="zip" type="xsd:decimal"/>
</xsd:sequence>
<xsd:attribute name="country" type="xsd:NMTOKEN"
fixed="US"/>
</xsd:complexType>
<xsd:complexType name="Items">
<xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="productName" type="xsd:string"/>
<xsd:element name="quantity">
<xsd:simpleType>
<xsd:restriction base="xsd:positiveInteger">
<xsd:maxExclusive value="100"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="USPrice" type="xsd:decimal"/>
<xsd:element ref="comment" minOccurs="0"/>
<xsd:element name="shipDate" type="xsd:date" minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="partNum" type="SKU" use="required"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>

<xsd:simpleType name="SKU">
<xsd:restriction base="xsd:string">
<xsd:pattern value="\d{3}-[A-Z]{2}"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>

Autotype from XML schema problems

Hello,
I am trying to autotype the following Xml schema:
http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-3
My build.xml contains:
<target name="autotype" >
     <autotype
          schemaFile="REL-5-MM7-1-3.xsd"
          targetNamespace="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-3"
          packageName="com.foo"
          keepGenerated = "True"
          destDir="output" />
</target>
1.
I run using ant but it fails..
SubmitRspTypeCodec.java:15: cannot resolve symbol
[autotype] symbol : class GenericResponseTypeCodec
[autotype] location: package soap
[autotype] extends javax.xml.soap.GenericResponseTypeCodec
weblogic.webservice.tools.build.WSBuildException: Failed to do type mapping -
with nested exception:
[weblogic.xml.schema.binding.BindingException: ERROR: during code compilation
- with nested exception:
[java.io.IOException: Compiler failed executable.exec]]
The interesting point is when i deleted following 3 lines from schema (line 413
to 415 in REL-5-MM7-1-3.xsd),
<xs:sequence>
     <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
no compile error is thrown.
2.
But the weird thing is that some of classes are not generated, for example SubmitReqType,
ReplaceReqType. This is because they reference RelativeOrAbsoluteDateType (line
367). And RelativeOrAbsoluteDateType contains the following union definition:
<xs:union memberTypes="xs:dateTime xs:duration"/>
i think that this union definition might cause problem but neither an error nor
a warning message is submitted from ant. It says successful but missing classes.
I am struggling with these 2 problems for days, any help would be appreciated.
Thanks,
aLi

Hi Ali,
I suspect that the reason you are having this problem is covered in the following
link:
http://e-docs.bea.com/wls/docs81/webserv/overview.html#1074641
I guess my question is, what else do you have in the build.xml that uses (or attempts
to use) the autotype Ant task? Are you trying to build a client (i.e. a JAX-RPC
static stub) for a web service? Is this for a WebLogic Web Service you want to
build? Or are you just trying to see if autotype can process the .xsd file, in
question? If so, the above link states why it currently won't work.
One alternative option, is to use a Workshop Schema project (or XMLBeans) to process
the .xsd file. I just did that, and it worked fine :-)
Regards,
Mike Wooten
"Ali Pakkan" <[email protected]> wrote:
>
Hello,
I am trying to autotype the following Xml schema:
http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-3
My build.xml contains:
<target name="autotype" >
     <autotype
          schemaFile="REL-5-MM7-1-3.xsd"
          targetNamespace="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-3"
          packageName="com.foo"
          keepGenerated = "True"
          destDir="output" />
</target>
1.
I run using ant but it fails..
SubmitRspTypeCodec.java:15: cannot resolve symbol
[autotype] symbol : class GenericResponseTypeCodec
[autotype] location: package soap
[autotype] extends javax.xml.soap.GenericResponseTypeCodec
weblogic.webservice.tools.build.WSBuildException: Failed to do type mapping
with nested exception:
[weblogic.xml.schema.binding.BindingException: ERROR: during code compilation
- with nested exception:
[java.io.IOException: Compiler failed executable.exec]]
The interesting point is when i deleted following 3 lines from schema
(line 413
to 415 in REL-5-MM7-1-3.xsd),
<xs:sequence>
     <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
no compile error is thrown.
2.
But the weird thing is that some of classes are not generated, for example
SubmitReqType,
ReplaceReqType. This is because they reference RelativeOrAbsoluteDateType
(line
367). And RelativeOrAbsoluteDateType contains the following union definition:
<xs:union memberTypes="xs:dateTime xs:duration"/>
i think that this union definition might cause problem but neither an
error nor
a warning message is submitted from ant. It says successful but missing
classes.
I am struggling with these 2 problems for days, any help would be appreciated.
Thanks,
aLi

XML schemas in subfolders problem

We have a large number of XML schemas and have partitioned them into different folders. This means that imported schemas are often located in a relative directory e.g.
<import namespace="http://www.xyz.com/schema/Staff" schemaLocation="../../Staff.xsd"/>
However, when building a BPEL app in JDeveloper, the JDeveloper Web Content/Miscellaneous Files folder doesn't seem to have the facility to create sub-folders and I get validation errors when importing the schema alongside the ones it imports. I'm not an expert JDeveloper user - is there something I've missed?
thanks Ash

Thanks, but actually I've yet to find that problem, as I haven't even got to creating any jars or anything yet. To clarify:
Simply using the "Import" button in the BPEL structure window in JDeveloper, you get a single prompt to browse for a schema.
Once imported, it ends up in a Web Content/Miscellaneous Files folder alongside every other schema. So I get JDeveloper flagging errors because my schema references other schemas relative to directory folder e.g. "../../ref.xsd".

XML Schema include problem

Similar Messages

Maybe you are looking for