Build logic in to xml schema

Hi :
I would like know if there anyway to add some control logic in xml schema,
for example: i have 2 elements : <type> and <subType>. for <type> it can only take on one of the 3 values, "event", "classified" and "QandA" by using xs:enumeration
and if the user chooses "event" as the value for <type>, then <subtype> can only have 3 values "concert", "sales" and "lectures" like the following<type>event</type>
<subType>concert</subType>
sales
lecturesthen how should I write the rules for <subType> in xsd? i.e how do i build in the logic to check to see if "event" is selected for the value of <type>
please let me know.
Many thanks

I don't think schemas can do that.
There is a tool called SchemaTron that is designed to do things like that. You provide XPath statements that are either valid or invalid and it reports appropriately.
I've not used it, but am aware of its capabilities.
Dave Patterson

Similar Messages

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

How to Build a XML Schema myself ?

I have a large xml document to be parsed
DTD just can tell me whether the file is well-construct .
I want to build a xml schema...but I have no resourse about this .
can sb tell me the way ? better give me a sample .
null

I'd recommend getting started with a tool like XML Spy 3.5 from Altova (www.altova.com) or XML Authority from Extensibility (www.extensibility.com). I've used both and both are very capable.

Using XSDBuilder to build XML Schema objects

I want to parse an XML document using an XML Schema Definition that I provide explicitly to the parser, rather than one identified in the document being validated. It appears that I can create an XML Schema object using XSDBuilder, and give it to the XML parser using XMLParser.setXMLSchema(). The problem is that XSDBuilder.build() wants an XSD system ID that is a file, and I want to retrieve XSD documents from non-file-based stores. Ideally, I'd like to give the builder a stream containing the XSD, or barring that, provide a custom entity resolver that it can use. Any ideas how to go about doing that? Or am I going about this the wrong way?
Thanks for any advice,
markl
null

Hi,
I didn't test it wit XML Schema, but any parser that finds a system ID should call an implementation of EntityResolver that returns an InputSource for the system ID.
An InputSource is a wrapper around an InputStream and its url and it ssystemID.
An example for sun's parser is on http://www.s-line.de/homepages/gerd_castan/java/resolve.html
(I "tested" this code also with oracles DTD and Schema parser. This means that I used this code for oracle, too, but I didn't go through the debugger to see what it does.)
Cheers,
Gerd

Logical DS using RDF/XML schema?

Hi,
Does ALDSP 2.5 support creation of a logical data source using an RDF/XML schema?
Any pointers to this would be really helpful.
Thanks,
Vidya

Hi,
Firstly a briefing on what I am trying to accomplish:
1.In my experiment, I have a XML schema called CurDataModel, with which I have created a logical DS CurDataModel.ds
I have created an RDF equivalent of the XML schema and want to create another logical DS.
2.I did refer the SampleTutorial1.pdf Section 3.1 which describes how to create logical DS.
3.However when i try to import a pre-defined RDF/XML schema (CUR.rdf) as attached, I am unable to do it.
Regards
Vidya

Build XSD (XML Schema Defenition) from XML using Oracle SOAz

Hi:
I want to integrate Application A to Application B using Oracle SOA suite. Application A will give me a XML file. Application B will supports XSD. Can any one help me how to build XSD using existing XML in Oracle SOA suite?
Appreciate if you give me the steps.
Thanks,
RAO

You might want to ask this question in the SOA forum. To get there ...
at the top of this page you will see a set of links that look like "Forum Home » Technology Network Community » Certification".
Click on 'Forum Home' to get to the Forum Home page.
Then press Ctrl+F to enable search in your browser.
Enter SOA in the search box, and if you are using Internet Explorer you might want to press the Next button.
You will see a list
SOA & Process Management
SOA Suite
BPEL
Applications Integration using Oracle Fusion Middleware
Business Process Management Suite
More... You could click on 'SOA Suite' to chat with people who use the SOA Suite.
You could click on 'More...' to see whether there are other useful forums.
Just to satisfy my curiosity, why did you select the Certification forum for this question?

MII XML Schema

Hello,
Does anyone have (or can point me to) an XML Schema (.XSD) that describes the standard Rowsets/Rowset/Row structure of the MII XML document? I presumed it to be installed somewhere during the 11.5 installation, but if it is I can't find it.
Thanks in advance,
Dave

David,
I don't know where the schema would be either, but you can reverse engineer it pretty easily by just building a sample.
Build a Business Logic Services transaction similar to this:
Sequence_0
Create a SAP xMII XML Output action block of type Document . Configure it with some fields. I did it with field names same as their datatypes.
Sequence_1
Create a SAP xMII XML Output action block of type Row and configure it to Document_0.Output from the first action block. Create links to map some data to a field or two or all of them.
Sequence_2
Link Document_0.Output to a Tracer and when you execute your transaction, you will receive:
<?xml version="1.0" encoding="UTF-8"?>
<Rowsets DateCreated="2008-04-21T16:20:49" EndDate="2008-04-21T16:18:21" StartDate="2008-04-21T16:18:21" Version="12.0.2 Build(88)"><Rowset><Columns><Column Description="" MaxRange="1" MinRange="0" Name="DateTime" SQLDataType="93" SourceColumn="DateTime"/><Column Description="" MaxRange="1" MinRange="0" Name="String" SQLDataType="1" SourceColumn="String"/><Column Description="" MaxRange="1" MinRange="0" Name="Integer" SQLDataType="4" SourceColumn="Integer"/><Column Description="" MaxRange="1" MinRange="0" Name="Double" SQLDataType="8" SourceColumn="Double"/></Columns><Row><DateTime>2008-04-21T16:20:49</DateTime><String>String</String><Integer>99</Integer><Double>109.5446</Double></Row></Rowset></Rowsets>
This is your basic xMII XML structure.
Hope this helps.
Mike

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.

Can't import XML schema with ref to external namespace

In TopLink 10.1.3 Dev Preview 3 (build 041116), I have 2 simple schema files. One defines an element as a ref to an element in the other schema, so the ref points to an element in an external namespace. TopLink won't import this schema.
First schema, imports fine:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
   xmlns:xs="http://www.w3.org/2001/XMLSchema"
   targetNamespace="http://www.oracle.com/employee"
   xmlns="http://www.oracle.com/employee"
   elementFormDefault="qualified"
   attributeFormDefault="unqualified">
     <xs:element name="employee">
       <xs:complexType>
         <xs:sequence>
                <xs:element name="name" type="xs:string"/>
         </xs:sequence>
       </xs:complexType>
     </xs:element>
</xs:schema>
Second schema, fails import with "ERROR: null. Please check to ensure the document conforms to the XML Schema specification and try again":
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
   xmlns:xs="http://www.w3.org/2001/XMLSchema"
   targetNamespace="http://www.oracle.com/department"
   xmlns="http://www.oracle.com/department"
   xmlns:employee="http://www.oracle.com/employee"
   elementFormDefault="qualified"
   attributeFormDefault="unqualified">
   <xs:import
     namespace="http://www.oracle.com/employee"
         schemaLocation="employee.xsd"/>
   <xs:element name="department">
     <xs:complexType>
       <xs:sequence>
         <xs:element ref="employee:employee"         maxOccurs="unbounded"/>
       </xs:sequence>
     </xs:complexType>
   </xs:element>
</xs:schema>
Both schemas are valid according to the W3C schema validation checker at http://www.w3.org/2001/03/webdata/xsv.
I can work around the issue by putting the employee definitions into the department schema file so that all elements are in the same namespace. But I would like the schemas to be in separate files for better modularity and maintainability.
Am I doing something wrong? I would really like to be able to use references to external namespaces in my element definitions.
Thanks,
Dave

Hello David,
Apologies, but this is a bug in DP3 with respect to references to elements in imported namespaces. This has been fixed in current code, but until you get that, there are a couple ways to work around it:
==========================================================
1) Use an include rather than an import.
department.xsd
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
    targetNamespace="http://www.oracle.com/department"
    xmlns="http://www.oracle.com/department"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    elementFormDefault="qualified"
    attributeFormDefault="unqualified">
   <xs:include schemaLocation="employee.xsd"/>
   <xs:element name="department">
      <xs:complexType>
         <xs:sequence>
            <xs:element ref="employee" maxOccurs="unbounded"/>
         </xs:sequence>
      </xs:complexType>
   </xs:element>
</xs:schema>employee.xsd
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    targetNamespace="http://www.oracle.com/department"
    xmlns="http://www.oracle.com/department"
    elementFormDefault="qualified"
    attributeFormDefault="unqualified">
   <xs:element name="employee">
      <xs:complexType>
         <xs:sequence>
            <xs:element name="name" type="xs:string"/>
         </xs:sequence>
      </xs:complexType>
   </xs:element>
</xs:schema>You should only have to import the parent schema (i.e. department.xsd), as the included document will automatically be built in. Note that this works for imports as well, provided that there aren't nasty bugs blocking the process.
==========================================================
2. Build everything into the same document
department.xsd
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
    targetNamespace="http://www.oracle.com/department"
    xmlns="http://www.oracle.com/department"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    elementFormDefault="qualified"
    attributeFormDefault="unqualified">
   <xs:element name="department">
      <xs:complexType>
         <xs:sequence>
            <xs:element ref="employee" maxOccurs="unbounded"/>
         </xs:sequence>
      </xs:complexType>
   </xs:element>
   <xs:element name="employee">
      <xs:complexType>
         <xs:sequence>
            <xs:element name="name" type="xs:string"/>
         </xs:sequence>
      </xs:complexType>
   </xs:element>
</xs:schema>Obviously, this one won't work quite as well in some cases.
==========================================================
Until you can get to the latest code, I hope this helps some.
- Paul

Validating a xml document via dtd or xml schema

hi.
i am trying to validate a xml document's structure via dtd or xml schema. unfortunately i dont have a clue how to do this. although i read some documents about it i didnt find a way to it yet.
i am using dom4j to build a org.dom4j.Document from a String.
my expectations were like this:
- read data into string
- create org.dom4j.Document from a string
- after successfully creating the document calling document.validate(xmlSchema) throwing a ParseException (or something like this when the xml doesnt meet the requirements given by the schema)
please help!

Class org.dom4j.Document does not have a validate() method.

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));

Java Stored Procedure SAXParser XML Schema Validation

Using Oracle XML Developers Kit 10.2.0.2.0 - Production.
Attempting to validate using XML Schema in a Java stored procedure with the code:
               if ( schemaDoc == null )
                    // Obtain default connection
                    Connection conn = new OracleDriver().defaultConnection();
                    OraclePreparedStatement stmt = (OraclePreparedStatement) conn.prepareStatement("SELECT XmlDocObj FROM XmlDoc WHERE XmlDocNbr = 2");
                    OracleResultSet rset = (OracleResultSet)stmt.executeQuery();
                    if ( rset.next() )
                         // get the XMLType
                         XMLType schemaXml = (XMLType)rset.getObject(1);
                         XSDBuilder builder = new XSDBuilder();
                         XMLSchema schemaDoc = (XMLSchema)builder.build(new InputSource(schemaXml.getInputStream()));
               if ( inst == null )
                    inst = new ValidateCoreRequest();
               ErrorHandlerImpl handler = inst.getNewErrorHandler();
SAXParser saxParser = new SAXParser();
saxParser.setXMLSchema(schemaDoc);
saxParser.setValidationMode(XMLParser.SCHEMA_VALIDATION);
saxParser.setErrorHandler(handler);
saxParser.parse(new InputSource(new StringReader(docStr)));
if( handler.validationError )
                    errorMsg[0] = handler.saxParseException.getMessage().substring(0, Math.min(199, handler.saxParseException.getMessage().length()));
Never reports validation errors in the XML. Although the XDK Programmers Guide states "...you can use
the oracle.xml.parser.schema.XSDBuilder class to build an XML schema and
then configure the parser to use it by invoking the XMLParser.setXMLSchema()
method. In this case, the XML parser automatically sets the validation mode to
SCHEMA_STRICT_VALIDATION and ignores the schemaLocation and
noNamespaceSchemaLocation attributes." No validation seems to occur. I have tried to set an xsi:noNamespaceSchemaLocation attribute on the root XML node, but this results in URL errors if the URL is not valid or schema build errors if the URL is valid, but does not point to a real location.
It appears that without a schema location attribute, no schema validation occurs. Using setXMLSchema() with a database source does not seem to cause the schema location attributes to be ignored. At least for Java stored procedures.
Does XML Schema validation work in the database for externally referenced schemas?
Thank You,
Art

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Jan Vissers ([email protected]):
I have two schemas A and B. A contains a java stored procedure which calls a java stored procedure stored in B. Upon resolving the "A" Java Stored Procedures I get the following error:
ORA-29545: badly formed class: at offset 3093 of Adapter.TFADPBeschikbaarheid.sendAanvraag expecting a class-oracle.xml.parser.v2.XMLDocument but encountered a class-oracle.xml.parser.v2.XMLDocument.
... Question:
it is expecting something which it has in fact encountered... SO!!!! What is the error.
Thx,
Jan<HR></BLOCKQUOTE>
Try this:
Edit your XSU installation script located on lib directory of Oracle XSU's distribution:
Find the line:
loadjava -r -v -u $USER_PASSWORD xmlparserv2.jar
Replace by:
loadjava -r -v -g public -u $USER_PASSWORD xmlparserv2.jar
And installs your Oracle XSU again.
Best regards, Marcelo.

XML Schema any element

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

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

Specifying nested element with two different XML Schema

Hello,
I am trying to convert one xml file to another file. I figure data services would be great for this.
My problem relates to how to have a source xml file with a certain xml schema be transformed to one of a different xml schema. I cannot build the nested elements of the target schema.
From the source xml I only need four fields. But they need to be nested three levels in the target xml.
Source
<DRUG_PRODUCT_LST xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <DRUG_ITEM>
      <DRUG_PRODUCT_ID>113083</DRUG_PRODUCT_ID>
      <DIN_PDIN>2317559</DIN_PDIN>
      <HC_BRAND_NAME>PMS-SILDENAFIL</HC_BRAND_NAME>
      <HC_ATC_CODE>G04BE03</HC_ATC_CODE>
   </DRUG_ITEM>
<DRUG_PRODUCT_LST
Target
<?xml version="1.0" encoding="ISO-8859-1"?>
<CODES>
   <CODE_TYPES>
      <CODE_TYPE>
         <COD_CODE>113083</COD_CODE>
         <COD_DESCR>PMS-SILDENAFIL</COD_DESCR>
         <COD_SOURCE>G04BE03</COD_SOURCE>
         <COD_NPSA>2317559</COD_NPSA>
      </CODE_TYPE>
   </CODE_TYPES>
</CODES>
I have tried using an xml pipline to unnest the source, then use a query transform to re-nest for the target. But I do not know how to specify the input schemas.

Hello,
I am trying to convert one xml file to another file. I figure data services would be great for this.
My problem relates to how to have a source xml file with a certain xml schema be transformed to one of a different xml schema. I cannot build the nested elements of the target schema.
From the source xml I only need four fields. But they need to be nested three levels in the target xml.
Source
<DRUG_PRODUCT_LST xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <DRUG_ITEM>
      <DRUG_PRODUCT_ID>113083</DRUG_PRODUCT_ID>
      <DIN_PDIN>2317559</DIN_PDIN>
      <HC_BRAND_NAME>PMS-SILDENAFIL</HC_BRAND_NAME>
      <HC_ATC_CODE>G04BE03</HC_ATC_CODE>
   </DRUG_ITEM>
<DRUG_PRODUCT_LST
Target
<?xml version="1.0" encoding="ISO-8859-1"?>
<CODES>
   <CODE_TYPES>
      <CODE_TYPE>
         <COD_CODE>113083</COD_CODE>
         <COD_DESCR>PMS-SILDENAFIL</COD_DESCR>
         <COD_SOURCE>G04BE03</COD_SOURCE>
         <COD_NPSA>2317559</COD_NPSA>
      </CODE_TYPE>
   </CODE_TYPES>
</CODES>
I have tried using an xml pipline to unnest the source, then use a query transform to re-nest for the target. But I do not know how to specify the input schemas.

JAXB 1.3 can't parse W3 SOAP 2003-05 envelope XML schema

Hello,
I was trying to use JAXB to parse the MMAP schema from the SMS Forum
(http://www.smsforum.net/schemas/mmap/v1.0/mmap.xsd). I finally
tracked it down to XJC choking on the included SOAP envelope schema's
use of the xml:lang attribute for a tag called reasontext. Here's the
pared-down test case:
C:\java\src\baz>%JWSDP_HOME%\jaxb\bin\xjc.bat http://www.w3.org/2003/05/soap-envelope/soap-envelope.xsd
%JWSDP_HOME%\jaxb\bin\xjc.bat http://www.w3.org/2003/05/soap-envelope/soap-envelope.xsd
parsing a schema...
[ERROR] src-resolve: Cannot resolve the name 'xml:lang' to a(n) attribute declaration component.
line 97 of soap-envelope.xsd
[ERROR] src-ct.0.1: Complex Type Definition Representation Error for type 'reasontext'. Element 'attribute' is invalid, misplaced, or occurs too often.
line 97 of soap-envelope.xsd
Failed to parse a schema.
C:\java\src\baz>I believe that the relevant portions of the schemas and namespaces in
question are:
http://www.w3.org/2003/05/soap-envelope/soap-envelope.xsd
<xs:complexType name="reasontext">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute ref="xml:lang" use="required" />
</xs:extension>
</xs:simpleContent>
</xs:complexType>http://www.w3.org/2001/XMLSchema.xsd
<xs:complexType name="attribute" mixed="false">
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:sequence>
<xs:element name="simpleType" minOccurs="0" type="xs:localSimpleType" />
</xs:sequence>
<xs:attributeGroup ref="xs:defRef" />
<xs:attribute name="type" type="xs:QName" />
<xs:attribute name="use" use="optional" default="optional">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="prohibited" />
<xs:enumeration value="optional" />
<xs:enumeration value="required" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="default" type="xs:string" />
<xs:attribute name="fixed" type="xs:string" />
<xs:attribute name="form" type="xs:formChoice" />
</xs:extension>
</xs:complexContent>
</xs:complexType>http://www.w3.org/2001/XMLSchema.xsd
<xs:attributeGroup name="defRef">
<xs:annotation>
<xs:documentation>for element, group and attributeGroup, which both define and reference</xs:documentation>
</xs:annotation>
<xs:attribute name="name" type="xs:NCName" />
<xs:attribute name="ref" type="xs:QName" />
</xs:attributeGroup>http://www.w3.org/XML/1998/namespace
The namespace whose name is http://www.w3.org/XML/1998/namespace is
bound by definition to the prefix xml: according to Namespaces in XML,
W3C Recommendation 14 Jan 1999. Note that unlike all other XML
namespaces, both the name and the prefix are specified; i.e., if you
want XML 1.0 processors to recognize this namespace, you must use the
reserved prefix xml:.
xml:lang and xml:space
As of the last update of this document, the XML 1.0 Specification
defines two attribute names in this namespace:
xml:lang
Designed for identifying the human language used in the scope of the
element to which it's attached.
.I'm no XML schema expert, but it looks to me like "name" and "ref"
are both valid attributes for an <xs:attribute> tag and that the XML
namespace standard requires XML processors to recognize the xml:lang
attribute. Hence, this appears to me to be a bug in JAXB.
A secondary bug is that the original error message left the name of
the offending included schema blank:
C:\java\src\foo>d:\java\jwsdp\jwsdp-1.3\jaxb\bin\xjc.bat http://www.smsforum.net/schemas/mmap/v1.0/mmap.xsd
parsing a schema...
[ERROR] src-resolve: Cannot resolve the name 'xml:lang' to a(n) attribute declaration component.
line 97 of
[ERROR] src-ct.0.1: Complex Type Definition Representation Error for type 'reasontext'. Element 'attribute' is invalid, misplaced, or occurs too often.
line 97 of
Failed to parse a schema.
C:\java\src\foo>In case it helps with problem diagnosis, I'm running with J2SDK 1.4.2
and have copied the endorsed jar files into the JRE lib as instructured
with JAXB:
C:\java\src\baz>java -version
java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
C:\java\src\baz>dir %JAVA_HOME%\jre\lib\endorsed
dir %JAVA_HOME%\jre\lib\endorsed
Volume in drive D has no label.
Volume Serial Number is 70AE-6E52
Directory of D:\java\j2se\j2sdk1.4.2\jre\lib\endorsed
03/31/2004 09:41 AM    <DIR>          .
03/31/2004 09:41 AM    <DIR>          ..
03/29/2004 01:28 PM            56,619 dom.jar
03/29/2004 01:28 PM            60,963 sax.jar
03/29/2004 01:28 PM         2,823,241 xalan.jar
03/29/2004 01:28 PM         2,667,618 xercesImpl.jar
10/10/2003 06:36 PM         1,379,810 xsltc.jar
               6 File(s)      6,989,573 bytes
               2 Dir(s)   7,889,731,584 bytes free
C:\java\src\baz>I'm quite interested in the resolution of this issue as I'm stopped in
my tracks on progress here. Help with resolution, whether in JAXB or
my usage of it, will be much appreciated. I did a search of existing
issues but didn't notice a duplicate. Thanks in advance.

I have also come across a similar problem with validating an xml file with an xml:lang attribute. It seems to be common across the schema validation and dtd validation. I get the following error with both schema and dtd validation:
Validation Error Msg (0): unexpected attribute "xml:lang"
Validation Error Location (0): FreeFormText
The test file extract looks like this:
<FreeFormText xml:lang="EN">Pelle</FreeFormText>
The schema defines the node as:
<xs:complexType name="FreeFormText">
          <xs:simpleContent>
               <xs:extension base="FreeFormTextType">
                    <xs:attribute name="lang" type="xs:language"/>
               </xs:extension>
          </xs:simpleContent>
</xs:complexType>
and the dtd defines the node as:
<!ELEMENT FreeFormText
     (#PCDATA)>
<!ATTLIST FreeFormText xml:lang CDATA #IMPLIED >
This looks like a bug in JAXB to me aswell. Any help on it would be much appreciated as i am also stuck.

Build logic in to xml schema

Similar Messages

Maybe you are looking for