Create xml from a collection type

can anyone please explain me how to create an xml from a neseted table

Hi Mario,
Thanks for letting us know about this problem. I have logged a bug on this.
If you should find any more problems like this, please let us know.
Thanks,
David

Similar Messages

Losing datatype definition from a collection type

Hi,
When I reload a model design from an xml repository, I am losing the datatype definition from a collection type.
It goes like this:
- In a collection type, the datatype is selected from a list of structure types (pre-defined).
- I save the whole model.
- So far, the datatype assignment is kept.
- If I exit from Data Modeler, the next time I reload the saved model, the collection datatype definition is lost...
Does anyone know how to resolve this issue?
Note: this looks very similar to a previous thread named 'Losing source-target mapping from a data flow diagram process'.
Thanks,
/Mario

Hi Mario,
Thanks for letting us know about this problem. I have logged a bug on this.
If you should find any more problems like this, please let us know.
Thanks,
David

Creating XML from raw data

I am trying to create xml from raw data. It works well in the format builder but
when I instanciate the MFLObject and run convert to xml, the output only contains
wrappers for my first field described in the mfl. Are there any known issues
using this progmattic conversion to XML.
My mfl is the following:
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE MessageFormat SYSTEM 'mfl.dtd'>

<MessageFormat name='BossRecord' version='2.01'>
<FieldFormat name='Header' type='String' length='102' codepage='windows-1252'/>
<StructFormat name='TransactionControlRecord' delim='999'>
<FieldFormat name='TransactionTypeNumber' type='String' length='3' codepage='windows-1252'/>
<FieldFormat name='TransactionData' type='String' codepage='windows-1252'>
<LenField type='Numeric' length='4'/>
</FieldFormat>
</StructFormat>
<StructFormat name='Generic' repeat='*'>
<FieldFormat name='GenericTypeNumber' type='String' length='3' codepage='windows-1252'/>
<FieldFormat name='GenericData' type='String' codepage='windows-1252'>
<LenField type='Numeric' length='4'/>
</FieldFormat>
</StructFormat>
<FieldFormat name='IgnoreTheRest' type='Filler' optional='y' length='1' repeat='*'>

</FieldFormat>
</MessageFormat>
Are there any issues with this that are easy to spot?
Here is some sample output:
_BossRecordDoc : <BossRecord>
<Header>0601uskyloupw7vu0 IBVRTR 000006RSQ1010246000000000000020436000001-01-01-00.00.00.00000000000100170</Header>
<Header>90100581D4EBC00AA3C18629ACA0004AC02E54BD289357023141961111F1111 99900207141D4EBC00AA3C18629ACA0004AC0</Header>
<Header>2E54BD2893570231RIBBONS & BUTTONS 9 00000000000010.50CAD00000000000000.5</Header>
<Header>0USD00000000000000.00USD00000000000077.00CAD 0CAUS00000000000000.91KGSA215D100CF3C18619AC</Header>
<Header>90004AC02E54B 01 0001-0</Header>
<Header>1-012003-04-072003-06-2501P/P03003984196000010100000000000000.00CAD 00
FR00000000000000</Header>
<Header>.0000000000000000000.00KGS00000000000000.00USD 00UPS T1</Header>
<Header>0001-01-010001-01-01 0 000000000000000.00000000000000000.00USD0</Header>
<Header>000000000000000.00 1 22222222222220 0100304061DC30500AA3C18629ACA</Header>
<Header>0004AC02E54B1D4EBC00AA3C18629ACA0004AC02E54B</Header>
<Header> 0010001-01-01 00000000000000.00USD00</Header>
<Header>000000000000.00CAD00000000000010.00CAD</Header>
<Header> 00000000000010.00CAD000000000000000010001-01-01K00404862A8D2C00AA3C186</Header>
<Header>29ACA0004AC02E54B1DC30500AA3C18629ACA0004AC02E54B001 PURPLE RIBBONS</Header>
It just keeps finding my first record instead of finding the remaing structure.
I appreciate any help.
Thanks,
Michael

Okay, I've got some coding off a site that looks like it will do what I want. It's quite a robust applications which will do more than I need but as long as it does at least what I want, i could care less. As it will extract files from the datastream for me, it is going to save them to disk.
I believe I have to specify a directory to save it to. I believe this is the line I'm going to modify, so assuming that's the case, how do I specify a directory here:
private File fileOutPutDirectory = null;
Do I have to use absolute paths or can I use relative. Also, what directory construct is expected by java? Anyone with an example of what urls are supposed to look like in this case?
Thanks,
destin

Creating XML from JDBC resultset

Can anyone give me a pointer as the best way to create XML from a JDBC resultset. I have told that XSU cannot be used as it is vendor specific and ties us to Oracle (yawn, yawn).
Any ideas welcomed.

import javax.xml.parsers.*;
import org.w3.dom.*;
import javax.xml.dom.*;
import javax.xml.dom.source.*;
import javax.xml.dom.stream.*;
import java.sql.*;
public class CreateXML{
DocumentBuilderFactory dbf=DocumentBuilderFactory.newInstance();
DocumentBuilder db=dbf.newDocumentBuilder();
Document doc=db.newDocument();
Element root=doc.createElement("root_element");
// coonect to database
//get resultset metadata rsmd
while(rs.next()){
Element row=doc.createElement("row");
for(int j=1;j<=rsmd.getColumnCount();j++){
String colName=rsmd.getCoulmName(j);
String colValue=rs.getString(j);
Element e=doc.createElement(colName);
e.appendChild(doc.createTextNode(colValue));
row.appendChild(e);
root.appendChild(row);
doc.appendChild(root);
//You can now use XSLT to generate xml file thus:
TransformerFactory tmf=TransformerFactory.newInstance();
Transformer tf=tmf.newTransformer();
DOMSource source=new DOMSource(doc);
StreamResult result=new StreamResult("name of file for output");
tf.transform(source,result);
// of course exceptions will have to be caught in this code.

Not able to create XML from an existing relational database

Hi,
I am trying to create and xml from an existing relational database. I am not able to get any XML data, I receive "XMLTYPE()" as the result.
Here's the query -
SQL> select o.order_id, XMLELEMENT("order", XMLATTRIBUTES(o.order_id as ID)) AS "result" from order_
info o where order_id=2793;
ORDER_ID
result()
+2793+
XMLTYPE()
I was expecting to get +<order id=2793 />+ instead of XMLTYPE().
I am using -
SQLPlus: Release 9.0.1.0.1*
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
I have also run some checks to confirm XML DB installation -
SQL> select 1 from all_users where username = 'XDB';
+1+
+1+
SQL> desc RESOURCE_VIEW;
Name                                      Null?    Type
RES                                                SYS.XMLTYPE
ANY_PATH                                           VARCHAR2(4000)
RESID                                              RAW(16)
I think, I have something wrong with installation or configuration.
Any idea about what have I done wrong here?

Works fine now. Got the result "<order ID="2793"></order>".
Thanks. :-)

Problems with "import from catalog" & "collection type mismatch"

I'm attempting to keep 2 catalogs on 2 different computers sunchronized. I'm exporting photos
and collections (actually a web gallery) from one computer to another, and
I'm getting a "collection type mismatch" error, that prevents the photos from being a
dded to the collection. I've exported and imported the flash gallery template
from one system to the other to make sure the templates were identical. A
ll the photos, keywords, and attributes seem to be imported properly, but the photos aren't added
to the collection. Anyone having success exporting/importing collections between computers?
I'm using LR 2.7 on Win 7 & Vista.
Thanks,
Mark

Thanks Dorin. I tested it with a "regular" collection, and it works.
I hope they fix this in v. 3 too!

Create String from all Collection Items

Hi all, I've been using Project Siena for the last week and I'm having a lot of fun with it.
Right now, I'm having a problem creating a string comprised of all the rows of a particular collection.
I am trying to generate the string for an email body. So far I have a 1 column collection called EmailCollection. It consists of rows of text with the appropriate URL Encoded characters. I would like to be able to export all the rows of this
collection to a string, and then add this string into the Launch(mailto:) body variable.
Let me know if I'm not being clear with this, and thanks for any help in advance!
Elliot

Thanks for the reply, StonyArc. I actually used your original thread to get me started until I ran into problems with exporting the entire single column collection to a concatenated string. I found a way to get it working, though it's not an elegant solution
and it wont work if the number of rows in the collection changes.
I'll try to explain it here, and if anyone else can think of a better way, I'd like to try it :)
I needed to create an URL encoded string for my emails which consisted of the relevant pricing information from a Collection with 8 rows called NewPricingCollection.
Collect(EmailPricing, Substitute(Substitute(Substitute(Concatenate(NewPricingCollection!SetupItem,": ", NewPricingCollection!NewAmount, " ", NewPricingCollection!UnitType, "s ($", NewPricingCollection!TotalPrice, ")"), " ", "%20"), "$", "%24"), ":", "%3A"));
This created a single column collection with 8 rows which looked like this: SetupItem: 5 Units ($TotalPrice). I used the substitute function to replace the non-URL friendly characters with their encoded equivalents. I'm not sure if this is the best
practice use of the Substitute function by the way.
Once I had the Single Column Collection, I couldn't find a way to concatenate the contents of each row into a single string. I was able to use the Lookup function to retrieve the first row of the collection, but that was it. Note that I may be using the
lookup function incorrectly too :)
I ended up using Last and LastN Functions to retrieve the specified number of rows from the end of the collection. Then I used the Lookup function to retrieve the string from the first row of each retrieved collection, then concatenated it together as a
single string - along with the rest of the email body.
LookUp(EmailPricing, Result in EmailPricing, Result) & "%0A" & LookUp(LastN(EmailPricing,7), Result in EmailPricing, Result) & "%0A" & LookUp(LastN(EmailPricing,6), Result in EmailPricing, Result) & "%0A" & LookUp(LastN(EmailPricing,5), Result in EmailPricing, Result) & "%0A" & LookUp(LastN(EmailPricing,4), Result in EmailPricing, Result) & "%0A" & LookUp(LastN(EmailPricing,3), Result in EmailPricing, Result) & "%0A" & LookUp(LastN(EmailPricing,2), Result in EmailPricing, Result) & "%0A" & LookUp(LastN(EmailPricing,1), Result in EmailPricing, Result)
This created a string that looked like this inside of an email body:
SetupItem1: 5 Units ($TotalPrice)
SetupItem2: 5 Units ($TotalPrice)
SetupItem3: 5 Units ($TotalPrice)
SetupItem4: 5 Units ($TotalPrice)
SetupItem5: 5 Units ($TotalPrice)
SetupItem6: 5 Units ($TotalPrice)
SetupItem7: 5 Units ($TotalPrice)
SetupItem8: 5 Units ($TotalPrice)
As you can see it will only work correctly with a collection of 8 rows, so if the number of items changes, then I'll need to find a better solution.

Create XML from XSD

Hi,
Is it possible to create and populate XML from an XSD without knowing what the XSD elements are beforehand (all the examples appear to know what the input XSD will be, and therefore know what the set and get methods should be called)?
Can a user browse for an xsd to input, and the java will dynamically create the get methods, and be able to create instances and populate variables before converting to XML?
I have looked at JAXB and the purchase.order examples mainly, and it appears the input XSD was known before writing the java to populate the variables.
Thanks
John

Hi,
Is it possible to create and populate XML from an XSD
without knowing what the XSD elements are beforehand
(all the examples appear to know what the input XSD
will be, and therefore know what the set and get
methods should be called)? I think it is possible--you would have to recompile each time (unless you can dynamically recompile, which would be neat), but using the classes getMethod() function, you can list all the methods. You would then have to do some tricky logic to determine which of the getMethods you want (for example NOT getClass()), and you can basically call them in sequence. You also need to worry about handling lists & recursively call xxxType classes.
I'm experimenting with this, and it can get a little frustrating because there are a lot of odd cases to handle (for example, while setting the elements of a list, you need to actually get the list & add elements to it), but I think it's possible.
>
Can a user browse for an xsd to input, and the java
will dynamically create the get methods, and be able
to create instances and populate variables before
converting to XML?
What I'm puzzled about is where you'd get the data to populate the variables? Perhaps a database, or a bean? If you just want to make a test xml file, then it doesn't matter, but with real data, I think you'd still have to change how you actually get the variables you want to populate the xml file with, right? In other words, if your schema changed, the parameters you're passing to the set methods would change as well.
Maybe we'll see some more packages in the future to make this task easier.

Creating XML from query result (how?)

Hi,
It's a very general question. That is the simplest way to create XML containing data returned by a query?
I've got 3 tables: 2 primary and a linked table. One of the primary tables contains a CLOB column. I need to export the tables to a XML file. That is the simplest way to do that? (There is many XML-related functions in Oracle XML DB and I don't know which may be good.)
Thanks in advance,
JackK

That is the simplest way to create XML containing data returned by a query?Simplest:
SQL> set long 10000
SQL> set pages 5000
SQL> show user
USER is "SYS"
SQL> select XMLTYPE(CURSOR(select * from user_objects where rownum = 1)) as SIMPLEST
2 from dual;
SIMPLEST
<?xml version="1.0"?>
<ROWSET>
<ROW>
    <OBJECT_NAME>ICOL$</OBJECT_NAME>
    <OBJECT_ID>20</OBJECT_ID>
    <DATA_OBJECT_ID>2</DATA_OBJECT_ID>
    <OBJECT_TYPE>TABLE</OBJECT_TYPE>
    <CREATED>16-JAN-13</CREATED>
    <LAST_DDL_TIME>16-JAN-13</LAST_DDL_TIME>
    <TIMESTAMP>2013-01-16:10:03:32</TIMESTAMP>
    <STATUS>VALID</STATUS>
    <TEMPORARY>N</TEMPORARY>
    <GENERATED>N</GENERATED>
    <SECONDARY>N</SECONDARY>
    <NAMESPACE>1</NAMESPACE>
</ROW>
</ROWSET>Edited by: Marco Gralike on Mar 13, 2013 1:59 PM

Creating XML from large result sets

We are trying to create XML docs from queries that return somewhere in the neighborhood of 13000+ rows, each with as many as 30 columns. It seems someplace deep within the xmlgen utility or the xsu methods, we throw an OutOfMemoryError. This happens whether we run as a java stored procedure, a pl/sql stored procedure, pl/sql script or java servlet. It looks like the top of the stack shows the problem occurs trying to extendCapacity in a StringBuffer. We're running 8.1.6 with java 1.2.2 and xsu 1.2. Has anyone had to query large amounts of data like this and if so, how did you go about it? Is there a slick way to break things up and then string everything back into 1 big xml doc? Any help would be greatly appreciated. Thanks.

I guess you can use pagination,
either using xsu or Top N Queries and then you could merge all the pages in an unique XML or DOM tree prior to persist it to disk.
With XSU:
Go to the following link for a clear explanation:
<http://technet.oracle.com/docs/products/oracle8i/doc_library/817_doc/appdev.817/a86030/adx04x11.htm#1008351>
With Top N queries:
Go to the following thread of this forum to see a similar question I raised and it was answered in detail:
<http://technet.oracle.com:89/ubb/Forum11/HTML/004711.html>
- Jose Angel -

Creating XML from XSD, Only create The First Element

Hi,
I create a XML File from a xsd schema by this way:
            DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
          factory.setNamespaceAware(true);
          factory.setValidating(true);
               factory.setAttribute(JAXP_SCHEMA_LANGUAGE,W3C_XML_SCHEMA);
               factory.setAttribute(JAXP_SCHEMA_SOURCE, new File(MY_SCHEMA));
                DocumentBuilder documentBuilder =factory.newDocumentBuilder();
          documentBuilder.setErrorHandler(new SimpleDOMHandler());
          Document parse = documentBuilder.parse(new File(MY_XML));The first lines of the schema:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
     targetNamespace="http://gencat.net/scsp/esquemes/peticion"
     elementFormDefault="qualified" attributeFormDefault="unqualified"
     id="Peticio" xmlns:p="http://gencat.net/scsp/esquemes/peticion">
     <xs:element name="Apellido1">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:maxLength value="40" />
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="Apellido2">
        .............................The problem is that the created document only have the first element "Apellido1". I dont know if it is a wrong xsd, or i'm using a bad way to do it.
Thanks a lot, and apologize for my english

Hi,
Is it possible to create and populate XML from an XSD
without knowing what the XSD elements are beforehand
(all the examples appear to know what the input XSD
will be, and therefore know what the set and get
methods should be called)? I think it is possible--you would have to recompile each time (unless you can dynamically recompile, which would be neat), but using the classes getMethod() function, you can list all the methods. You would then have to do some tricky logic to determine which of the getMethods you want (for example NOT getClass()), and you can basically call them in sequence. You also need to worry about handling lists & recursively call xxxType classes.
I'm experimenting with this, and it can get a little frustrating because there are a lot of odd cases to handle (for example, while setting the elements of a list, you need to actually get the list & add elements to it), but I think it's possible.
>
Can a user browse for an xsd to input, and the java
will dynamically create the get methods, and be able
to create instances and populate variables before
converting to XML?
What I'm puzzled about is where you'd get the data to populate the variables? Perhaps a database, or a bean? If you just want to make a test xml file, then it doesn't matter, but with real data, I think you'd still have to change how you actually get the variables you want to populate the xml file with, right? In other words, if your schema changed, the parameters you're passing to the set methods would change as well.
Maybe we'll see some more packages in the future to make this task easier.

Creating XML from Oracle Tables

Would it be possible to post me a snapshot of the ODI Flow diagram for an Oracle to XML conversion? Does the staging area have to be on the Target (XML)? What KMs & CM should be used? Can the XML be written straight back to an .xml file? What should the XML Schema look like?
These are the KMs I use: LKM-SQL to SQL; IKM-SQL Incremental Update; CKM-SQL.
My flow is straight from source (oracle) to target (xml), with staging area on target (doesn't feel right).
My Oracle Dataserver & Schema work fine. Not sure about the XML dataserver setup though - I think this is where the problem lies. These are my JDBC settings:
- com.sunopsis.jdbc.driver.xml.SnpsXmlDriver
- jdbc:snps:xml?f=E:\Oracle ODI\Member.xsd
I am evaluating ODI for a client and I wanted to throw together a quick demo showing how easily ODI can generate XML from any source. I know this is the case as I understand the concept of ODI's components - just haven't had time to read manuals thoroughly.
Many thanks for your help,
Steve

Hello,
1. Try to test the connection to the XML dataserver.
2. Create a model and reverse-engineer this dataserver. You'll see what the XML structure is mapped to immediately.
3. Integrate data to this model (using standard KM targeting "SQL").
You can put the staging area on the Oracle source or in the XML driver if you want. Both solutions will work.
just haven't had time to read manuals thoroughly.I think you should quickly read the "Sunopsis ODI with... XML" section in the manual.
It is not very long and very helpful. Have also a quick look at the XML driver documentation.
Regards,
-FX

How to create XML from relational tables based on an XML Schema ?

There is no automated way in Oracle XML DB to define an automatic mapping between a set of columns in some existing relational tables and the elements and attributres defined by an XML Schema.
However it is easy solve this problem by using the SQL/XML operators (XMLAGG, XMLELEMENT, XMLFOREST, XMLATTRIBUTES, etc) to generate XML documents that are compliant with an XML Schema directly from a SQL statement.
If the XML Schema is registered with Oracle XML DB and the appropraite Schema Location information is added into the generated document using XMLAttributes then it becomes very easy to ensure that the generated documents are valid.
The following example show an easy way to do this by creating an XML View that contains the documents to be validated.
SQL> drop table PURCHASEORDER_LINEITEM
2 /
Table dropped.
SQL> drop table PURCHASEORDER_REJECTION
2 /
Table dropped.
SQL> drop table PURCHASEORDER_SHIPPING
2 /
Table dropped.
SQL> drop TABLE PURCHASEORDER_ACTION
2 /
Table dropped.
SQL> drop TABLE PURCHASEORDER_TABLE
2 /
Table dropped.
SQL> create table PURCHASEORDER_TABLE
2 (
3   REFERENCE                                          VARCHAR2(28),
4   PRIMARY KEY ("REFERENCE"),
5   REQUESTER                                          VARCHAR2(48),
6   USERID                                             VARCHAR2(32),
7   COSTCENTER                                         VARCHAR2(3),
8   SPECIALINSTRUCTIONS                                VARCHAR2(2048)
9 )
10 /
Table created.
SQL> create table PURCHASEORDER_ACTION
2 (
3   REFERENCE,
4   FOREIGN KEY ("REFERENCE")                          REFERENCES "PURCHASEORDER_TABLE" ("REFERENCE") ON DELETE CASCADE,
5   ACTIONEDBY                                         VARCHAR2(32),
6   DATEACTIONED                                       DATE
7 )
8 /
Table created.
SQL> create table PURCHASEORDER_SHIPPING
2 (
3   REFERENCE,
4   FOREIGN KEY ("REFERENCE")                          REFERENCES "PURCHASEORDER_TABLE" ("REFERENCE") ON DELETE CASCADE,
5   PRIMARY KEY ("REFERENCE"),
6   SHIPTONAME                                         VARCHAR2(48),
7   ADDRESS                                            VARCHAR2(512),
8   PHONE                                              VARCHAR2(32)
9 )
10 /
Table created.
SQL> create table PURCHASEORDER_REJECTION
2 (
3   REFERENCE,
4   FOREIGN KEY ("REFERENCE")                          REFERENCES "PURCHASEORDER_TABLE" ("REFERENCE") ON DELETE CASCADE,
5   PRIMARY KEY ("REFERENCE"),
6   REJECTEDBY                                         VARCHAR2(32),
7   DATEREJECTED                                       DATE,
8   COMMENTS                                           VARCHAR2(2048)
9 )
10 /
Table created.
SQL> create table PURCHASEORDER_LINEITEM
2 (
3   REFERENCE,
4   FOREIGN KEY ("REFERENCE")                          REFERENCES "PURCHASEORDER_TABLE" ("REFERENCE") ON DELETE CASCADE,
5   LINENO                                             NUMBER(10),
6   PRIMARY KEY ("REFERENCE","LINENO"),
7   UPC                                                   VARCHAR2(14),
8   DESCRIPTION                                        VARCHAR2(128),
9   QUANTITY                                           NUMBER(10),
10   UNITPRICE                                          NUMBER(12,2)
11 )
12 /
Table created.
SQL> insert into PURCHASEORDER_TABLE values ('SMCCAIN-20030109123335470PDT','Samuel B. McCain','SMCCAIN','A10','Courier')
2 /
1 row created.
SQL> insert into PURCHASEORDER_ACTION values ('SMCCAIN-20030109123335470PDT','SVOLLMAN',NULL)
2 /
1 row created.
SQL> insert into PURCHASEORDER_SHIPPING values ('SMCCAIN-20030109123335470PDT','Samuel B. McCain','800 Bridge Parkway,Redwood Shores,CA,9406
5,USA','650 506 7800')
2 /
1 row created.
SQL> insert into PURCHASEORDER_REJECTION values ('SMCCAIN-20030109123335470PDT',null,null,null)
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','1','715515010320','Life of Brian - Monty Python''s','2','39.
95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','2','37429145227','The Night Porter','2','29.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','3','37429128121','Oliver Twist','1','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','4','715515012720','Notorious','4','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','5','715515012928','In the Mood for Love','3','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','6','37429130926','Alphaville','2','29.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','7','37429166529','General Idi Amin Dada','4','29.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','8','715515012928','In the Mood for Love','3','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','9','715515009423','Flesh for Frankenstein','3','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','10','715515008976','The Killer','1','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','11','37429167922','Ballad of a Soldier','2','29.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','12','37429158623','Ordet','2','0')
2 /
1 row created.
SQL> var schemaPath varchar2(256)
SQL> --
SQL> begin
2    :schemaURL := 'http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd';
3    :schemaPath := '/public/purchaseOrder.xsd';
4 end;
5 /
PL/SQL procedure successfully completed.
SQL> call dbms_xmlSchema.deleteSchema(:schemaURL,4)
2 /
Call completed.
SQL> declare
2    res boolean;
3    xmlSchema xmlType := xmlType(
4 '
5 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" version="1.0" xdb:storeVarrayAsTable="tr
ue">
6          <xs:element name="PurchaseOrder" type="PurchaseOrderType" xdb:defaultTable="PURCHASEORDER"/>
7          <xs:complexType name="PurchaseOrderType" xdb:SQLType="PURCHASEORDER_T" xdb:maintainDOM="false">
8                  <xs:sequence>
9                          <xs:element name="Reference" type="ReferenceType" xdb:SQLName="REFERENCE"/>
10                          <xs:element name="Actions" type="ActionsType" xdb:SQLName="ACTIONS"/>
11                          <xs:element name="Reject" type="RejectionType" minOccurs="0" xdb:SQLName="REJECTION"/>
12                          <xs:element name="Requestor" type="RequestorType" xdb:SQLName="REQUESTOR"/>
13                          <xs:element name="User" type="UserType" xdb:SQLName="USERID"/>
14                          <xs:element name="CostCenter" type="CostCenterType" xdb:SQLName="COST_CENTER"/>
15                          <xs:element name="ShippingInstructions" type="ShippingInstructionsType" xdb:SQLName="SHIPPING_INSTRUCTIONS"/>
16                          <xs:element name="SpecialInstructions" type="SpecialInstructionsType" xdb:SQLName="SPECIAL_INSTRUCTIONS"/>
17                          <xs:element name="LineItems" type="LineItemsType" xdb:SQLName="LINEITEMS"/>
18                  </xs:sequence>
19          </xs:complexType>
20          <xs:complexType name="LineItemsType" xdb:SQLType="LINEITEMS_T" xdb:maintainDOM="false">
21                  <xs:sequence>
22                          <xs:element name="LineItem" type="LineItemType" maxOccurs="unbounded" xdb:SQLName="LINEITEM" xdb:SQLCollType="L
INEITEM_V"/>
23                  </xs:sequence>
24          </xs:complexType>
25          <xs:complexType name="LineItemType" xdb:SQLType="LINEITEM_T" xdb:maintainDOM="false">
26                  <xs:sequence>
27                          <xs:element name="Description" type="DescriptionType" xdb:SQLName="DESRIPTION"/>
28                          <xs:element name="Part" type="PartType" xdb:SQLName="PART"/>
29                  </xs:sequence>
30                  <xs:attribute name="ItemNumber" type="xs:integer" xdb:SQLName="ITEMNUMBER" xdb:SQLType="NUMBER"/>
31          </xs:complexType>
32          <xs:complexType name="PartType" xdb:SQLType="PART_T" xdb:maintainDOM="false">
33                  <xs:attribute name="Id" xdb:SQLName="PART_NUMBER" xdb:SQLType="VARCHAR2">
34                          <xs:simpleType>
35                                  <xs:restriction base="xs:string">
36                                          <xs:minLength value="10"/>
37                                          <xs:maxLength value="14"/>
38                                  </xs:restriction>
39                          </xs:simpleType>
40                  </xs:attribute>
41                  <xs:attribute name="Quantity" type="moneyType" xdb:SQLName="QUANTITY"/>
42                  <xs:attribute name="UnitPrice" type="quantityType" xdb:SQLName="UNITPRICE"/>
43          </xs:complexType>
44          <xs:simpleType name="ReferenceType">
45                  <xs:restriction base="xs:string">
46                          <xs:minLength value="18"/>
47                          <xs:maxLength value="30"/>
48                  </xs:restriction>
49          </xs:simpleType>
50          <xs:complexType name="ActionsType" xdb:SQLType="ACTIONS_T" xdb:maintainDOM="false">
51                  <xs:sequence>
52                          <xs:element name="Action" maxOccurs="4" xdb:SQLName="ACTION" xdb:SQLCollType="ACTION_V">
53                                  <xs:complexType xdb:SQLType="ACTION_T" xdb:maintainDOM="false">
54                                          <xs:sequence>
55                                                  <xs:element name="User" type="UserType" xdb:SQLName="ACTIONED_BY"/>
56                                                  <xs:element name="Date" type="DateType" minOccurs="0" xdb:SQLName="DATE_ACTIONED"/>
57                                          </xs:sequence>
58                                  </xs:complexType>
59                          </xs:element>
60                  </xs:sequence>
61          </xs:complexType>
62          <xs:complexType name="RejectionType" xdb:SQLType="REJECTION_T" xdb:maintainDOM="false">
63                  <xs:all>
64                          <xs:element name="User" type="UserType" minOccurs="0" xdb:SQLName="REJECTED_BY"/>
65                          <xs:element name="Date" type="DateType" minOccurs="0" xdb:SQLName="DATE_REJECTED"/>
66                          <xs:element name="Comments" type="CommentsType" minOccurs="0" xdb:SQLName="REASON_REJECTED"/>
67                  </xs:all>
68          </xs:complexType>
69          <xs:complexType name="ShippingInstructionsType" xdb:SQLType="SHIPPING_INSTRUCTIONS_T" xdb:maintainDOM="false">
70                  <xs:sequence>
71                          <xs:element name="name" type="NameType" minOccurs="0" xdb:SQLName="SHIP_TO_NAME"/>
72                          <xs:element name="address" type="AddressType" minOccurs="0" xdb:SQLName="SHIP_TO_ADDRESS"/>
73                          <xs:element name="telephone" type="TelephoneType" minOccurs="0" xdb:SQLName="SHIP_TO_PHONE"/>
74                  </xs:sequence>
75          </xs:complexType>
76          <xs:simpleType name="moneyType">
77                  <xs:restriction base="xs:decimal">
78                          <xs:fractionDigits value="2"/>
79                          <xs:totalDigits value="12"/>
80                  </xs:restriction>
81          </xs:simpleType>
82          <xs:simpleType name="quantityType">
83                  <xs:restriction base="xs:decimal">
84                          <xs:fractionDigits value="4"/>
85                          <xs:totalDigits value="8"/>
86                  </xs:restriction>
87          </xs:simpleType>
88          <xs:simpleType name="UserType">
89                  <xs:restriction base="xs:string">
90                          <xs:minLength value="1"/>
91                          <xs:maxLength value="10"/>
92                  </xs:restriction>
93          </xs:simpleType>
94          <xs:simpleType name="RequestorType">
95                  <xs:restriction base="xs:string">
96                          <xs:minLength value="0"/>
97                          <xs:maxLength value="128"/>
98                  </xs:restriction>
99          </xs:simpleType>
100          <xs:simpleType name="CostCenterType">
101                  <xs:restriction base="xs:string">
102                          <xs:minLength value="1"/>
103                          <xs:maxLength value="4"/>
104                  </xs:restriction>
105          </xs:simpleType>
106          <xs:simpleType name="VendorType">
107                  <xs:restriction base="xs:string">
108                          <xs:minLength value="0"/>
109                          <xs:maxLength value="20"/>
110                  </xs:restriction>
111          </xs:simpleType>
112          <xs:simpleType name="PurchaseOrderNumberType">
113                  <xs:restriction base="xs:integer"/>
114          </xs:simpleType>
115          <xs:simpleType name="SpecialInstructionsType">
116                  <xs:restriction base="xs:string">
117                          <xs:minLength value="0"/>
118                          <xs:maxLength value="2048"/>
119                  </xs:restriction>
120          </xs:simpleType>
121          <xs:simpleType name="NameType">
122                  <xs:restriction base="xs:string">
123                          <xs:minLength value="1"/>
124                          <xs:maxLength value="20"/>
125                  </xs:restriction>
126          </xs:simpleType>
127          <xs:simpleType name="AddressType">
128                  <xs:restriction base="xs:string">
129                          <xs:minLength value="1"/>
130                          <xs:maxLength value="256"/>
131                  </xs:restriction>
132          </xs:simpleType>
133          <xs:simpleType name="TelephoneType">
134                  <xs:restriction base="xs:string">
135                          <xs:minLength value="1"/>
136                          <xs:maxLength value="24"/>
137                  </xs:restriction>
138          </xs:simpleType>
139          <xs:simpleType name="DateType">
140                  <xs:restriction base="xs:date"/>
141          </xs:simpleType>
142          <xs:simpleType name="CommentsType">
143                  <xs:restriction base="xs:string">
144                          <xs:minLength value="1"/>
145                          <xs:maxLength value="2048"/>
146                  </xs:restriction>
147          </xs:simpleType>
148          <xs:simpleType name="DescriptionType">
149                  <xs:restriction base="xs:string">
150                          <xs:minLength value="1"/>
151                          <xs:maxLength value="256"/>
152                  </xs:restriction>
153          </xs:simpleType>
154 </xs:schema>
155 ');
156 begin
157    if (dbms_xdb.existsResource(:schemaPath)) then
158      dbms_xdb.deleteResource(:schemaPath);
159    end if;
160    res := dbms_xdb.createResource(:schemaPath,xmlSchema);
161 end;
162 /
PL/SQL procedure successfully completed.
SQL> begin
2    dbms_xmlschema.registerSchema
3    (
4      :schemaURL,
5      xdbURIType(:schemaPath).getClob(),
6      TRUE,TRUE,FALSE,FALSE
7    );
8 end;
9 /
PL/SQL procedure successfully completed.
SQL> create or replace view PURCHASEORDER_XML
2 of xmltype
3 xmlSCHEMA "http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd" Element "PurchaseOrder"
4 with object id
5 (
6    substr(extractValue(object_value,'/PurchaseOrder/Reference'),1,32)
7 )
8 as
9    select xmlElement
10           (
11             "PurchaseOrder",
12             xmlAttributes
13             (
14               'http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd' as "xsi:noNamespaceSchemaLocation",
15               'http://www.w3.org/2001/XMLSchema-instance' as "xmlns:xsi"
16             ),
17             xmlElement("Reference",p.REFERENCE),
18             xmlElement
19             (
20               "Actions",
21               ( select xmlAgg
22                        (
23                          xmlElement
24                          (
25                            "Action",
26                            xmlElement("User",ACTIONEDBY),
27                            case
28                              when DATEACTIONED is not null
29                              then xmlElement("Date",DATEACTIONED)
30                            end
31                          )
32                        )
33                   from PURCHASEORDER_ACTION a
34                  where a.REFERENCE = p.REFERENCE
35               )
36             ),
37             xmlElement
38             (
39               "Reject",
40                  xmlForest
41                  (
42                    REJECTEDBY as "User",
43                 DATEREJECTED as "Date",
44                    COMMENTS as "Comments"
45                  )
46             ),
47             xmlElement("Requestor",REQUESTER),
48             xmlElement("User",USERID),
49             xmlElement("CostCenter",COSTCENTER),
50             xmlElement
51             (
52               "ShippingInstructions",
53               xmlElement("name",SHIPTONAME),
54               xmlElement("address",ADDRESS),
55               xmlElement("telephone",PHONE)
56             ),
57             xmlElement("SpecialInstructions",SPECIALINSTRUCTIONS),
58             xmlElement
59             (
60               "LineItems",
61               ( select xmlAgg
62                        (
63                          xmlElement
64                          (
65                            "LineItem",
66                            xmlAttributes(LINENO as "ItemNumber"),
67                            xmlElement("Description",DESCRIPTION),
68                            xmlElement
69                            (
70                              "Part",
71                              xmlAttributes
72                              (
73                                UPC       as "Id",
74                                QUANTITY as "Quantity",
75                                UNITPRICE as "UnitPrice"
76                              )
77                            )
78                          )
79                        )
80                    from PURCHASEORDER_LINEITEM l
81                   where l.REFERENCE = p.REFERENCE
82               )
83             )
84           )
85      from PURCHASEORDER_TABLE p, PURCHASEORDER_REJECTION r, PURCHASEORDER_SHIPPING s
86     where r.REFERENCE = p.REFERENCE
87       and s.REFERENCE = p.REFERENCE
88 /
View created.
SQL> set long 10000 pages 0 lines 140
SQL> --
SQL> select x.object_value.extract('/*')
2    from PURCHASEORDER_XML x
3 /
<PurchaseOrder xsi:noNamespaceSchemaLocation="http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Reference>SMCCAIN-20030109123335470PDT</Reference>
<Actions>
    <Action>
      <User>SVOLLMAN</User>
    </Action>
</Actions>
<Reject/>
<Requestor>Samuel B. McCain</Requestor>
<User>SMCCAIN</User>
<CostCenter>A10</CostCenter>
<ShippingInstructions>
    <name>Samuel B. McCain</name>
    <address>800 Bridge Parkway,Redwood Shores,CA,94065,USA</address>
    <telephone>650 506 7800</telephone>
</ShippingInstructions>
<SpecialInstructions>Courier</SpecialInstructions>
<LineItems>
    <LineItem ItemNumber="1">
      <Description>Life of Brian - Monty Python's</Description>
      <Part Id="715515010320" Quantity="2" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="2">
      <Description>The Night Porter</Description>
      <Part Id="37429145227" Quantity="2" UnitPrice="29.95"/>
    </LineItem>
    <LineItem ItemNumber="3">
      <Description>Oliver Twist</Description>
      <Part Id="37429128121" Quantity="1" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="4">
      <Description>Notorious</Description>
      <Part Id="715515012720" Quantity="4" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="5">
      <Description>In the Mood for Love</Description>
      <Part Id="715515012928" Quantity="3" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="6">
      <Description>Alphaville</Description>
      <Part Id="37429130926" Quantity="2" UnitPrice="29.95"/>
    </LineItem>
    <LineItem ItemNumber="7">
      <Description>General Idi Amin Dada</Description>
      <Part Id="37429166529" Quantity="4" UnitPrice="29.95"/>
    </LineItem>
    <LineItem ItemNumber="8">
      <Description>In the Mood for Love</Description>
      <Part Id="715515012928" Quantity="3" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="9">
      <Description>Flesh for Frankenstein</Description>
      <Part Id="715515009423" Quantity="3" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="10">
      <Description>The Killer</Description>
      <Part Id="715515008976" Quantity="1" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="11">
      <Description>Ballad of a Soldier</Description>
      <Part Id="37429167922" Quantity="2" UnitPrice="29.95"/>
    </LineItem>
    <LineItem ItemNumber="12">
      <Description>Ordet</Description>
      <Part Id="37429158623" Quantity="2" UnitPrice="0"/>
    </LineItem>
</LineItems>
</PurchaseOrder>
SQL> begin
2    for x in (select object_value from PURCHASEORDER_XML) loop
3      x.object_value.schemaValidate();
4    end loop;
5 end;
6 /
PL/SQL procedure successfully completed.
SQL>

There is no automated way in Oracle XML DB to define an automatic mapping between a set of columns in some existing relational tables and the elements and attributres defined by an XML Schema.
However it is easy solve this problem by using the SQL/XML operators (XMLAGG, XMLELEMENT, XMLFOREST, XMLATTRIBUTES, etc) to generate XML documents that are compliant with an XML Schema directly from a SQL statement.
If the XML Schema is registered with Oracle XML DB and the appropraite Schema Location information is added into the generated document using XMLAttributes then it becomes very easy to ensure that the generated documents are valid.
The following example show an easy way to do this by creating an XML View that contains the documents to be validated.
SQL> drop table PURCHASEORDER_LINEITEM
2 /
Table dropped.
SQL> drop table PURCHASEORDER_REJECTION
2 /
Table dropped.
SQL> drop table PURCHASEORDER_SHIPPING
2 /
Table dropped.
SQL> drop TABLE PURCHASEORDER_ACTION
2 /
Table dropped.
SQL> drop TABLE PURCHASEORDER_TABLE
2 /
Table dropped.
SQL> create table PURCHASEORDER_TABLE
2 (
3   REFERENCE                                          VARCHAR2(28),
4   PRIMARY KEY ("REFERENCE"),
5   REQUESTER                                          VARCHAR2(48),
6   USERID                                             VARCHAR2(32),
7   COSTCENTER                                         VARCHAR2(3),
8   SPECIALINSTRUCTIONS                                VARCHAR2(2048)
9 )
10 /
Table created.
SQL> create table PURCHASEORDER_ACTION
2 (
3   REFERENCE,
4   FOREIGN KEY ("REFERENCE")                          REFERENCES "PURCHASEORDER_TABLE" ("REFERENCE") ON DELETE CASCADE,
5   ACTIONEDBY                                         VARCHAR2(32),
6   DATEACTIONED                                       DATE
7 )
8 /
Table created.
SQL> create table PURCHASEORDER_SHIPPING
2 (
3   REFERENCE,
4   FOREIGN KEY ("REFERENCE")                          REFERENCES "PURCHASEORDER_TABLE" ("REFERENCE") ON DELETE CASCADE,
5   PRIMARY KEY ("REFERENCE"),
6   SHIPTONAME                                         VARCHAR2(48),
7   ADDRESS                                            VARCHAR2(512),
8   PHONE                                              VARCHAR2(32)
9 )
10 /
Table created.
SQL> create table PURCHASEORDER_REJECTION
2 (
3   REFERENCE,
4   FOREIGN KEY ("REFERENCE")                          REFERENCES "PURCHASEORDER_TABLE" ("REFERENCE") ON DELETE CASCADE,
5   PRIMARY KEY ("REFERENCE"),
6   REJECTEDBY                                         VARCHAR2(32),
7   DATEREJECTED                                       DATE,
8   COMMENTS                                           VARCHAR2(2048)
9 )
10 /
Table created.
SQL> create table PURCHASEORDER_LINEITEM
2 (
3   REFERENCE,
4   FOREIGN KEY ("REFERENCE")                          REFERENCES "PURCHASEORDER_TABLE" ("REFERENCE") ON DELETE CASCADE,
5   LINENO                                             NUMBER(10),
6   PRIMARY KEY ("REFERENCE","LINENO"),
7   UPC                                                   VARCHAR2(14),
8   DESCRIPTION                                        VARCHAR2(128),
9   QUANTITY                                           NUMBER(10),
10   UNITPRICE                                          NUMBER(12,2)
11 )
12 /
Table created.
SQL> insert into PURCHASEORDER_TABLE values ('SMCCAIN-20030109123335470PDT','Samuel B. McCain','SMCCAIN','A10','Courier')
2 /
1 row created.
SQL> insert into PURCHASEORDER_ACTION values ('SMCCAIN-20030109123335470PDT','SVOLLMAN',NULL)
2 /
1 row created.
SQL> insert into PURCHASEORDER_SHIPPING values ('SMCCAIN-20030109123335470PDT','Samuel B. McCain','800 Bridge Parkway,Redwood Shores,CA,9406
5,USA','650 506 7800')
2 /
1 row created.
SQL> insert into PURCHASEORDER_REJECTION values ('SMCCAIN-20030109123335470PDT',null,null,null)
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','1','715515010320','Life of Brian - Monty Python''s','2','39.
95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','2','37429145227','The Night Porter','2','29.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','3','37429128121','Oliver Twist','1','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','4','715515012720','Notorious','4','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','5','715515012928','In the Mood for Love','3','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','6','37429130926','Alphaville','2','29.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','7','37429166529','General Idi Amin Dada','4','29.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','8','715515012928','In the Mood for Love','3','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','9','715515009423','Flesh for Frankenstein','3','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','10','715515008976','The Killer','1','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','11','37429167922','Ballad of a Soldier','2','29.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','12','37429158623','Ordet','2','0')
2 /
1 row created.
SQL> var schemaPath varchar2(256)
SQL> --
SQL> begin
2    :schemaURL := 'http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd';
3    :schemaPath := '/public/purchaseOrder.xsd';
4 end;
5 /
PL/SQL procedure successfully completed.
SQL> call dbms_xmlSchema.deleteSchema(:schemaURL,4)
2 /
Call completed.
SQL> declare
2    res boolean;
3    xmlSchema xmlType := xmlType(
4 '
5 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" version="1.0" xdb:storeVarrayAsTable="tr
ue">
6          <xs:element name="PurchaseOrder" type="PurchaseOrderType" xdb:defaultTable="PURCHASEORDER"/>
7          <xs:complexType name="PurchaseOrderType" xdb:SQLType="PURCHASEORDER_T" xdb:maintainDOM="false">
8                  <xs:sequence>
9                          <xs:element name="Reference" type="ReferenceType" xdb:SQLName="REFERENCE"/>
10                          <xs:element name="Actions" type="ActionsType" xdb:SQLName="ACTIONS"/>
11                          <xs:element name="Reject" type="RejectionType" minOccurs="0" xdb:SQLName="REJECTION"/>
12                          <xs:element name="Requestor" type="RequestorType" xdb:SQLName="REQUESTOR"/>
13                          <xs:element name="User" type="UserType" xdb:SQLName="USERID"/>
14                          <xs:element name="CostCenter" type="CostCenterType" xdb:SQLName="COST_CENTER"/>
15                          <xs:element name="ShippingInstructions" type="ShippingInstructionsType" xdb:SQLName="SHIPPING_INSTRUCTIONS"/>
16                          <xs:element name="SpecialInstructions" type="SpecialInstructionsType" xdb:SQLName="SPECIAL_INSTRUCTIONS"/>
17                          <xs:element name="LineItems" type="LineItemsType" xdb:SQLName="LINEITEMS"/>
18                  </xs:sequence>
19          </xs:complexType>
20          <xs:complexType name="LineItemsType" xdb:SQLType="LINEITEMS_T" xdb:maintainDOM="false">
21                  <xs:sequence>
22                          <xs:element name="LineItem" type="LineItemType" maxOccurs="unbounded" xdb:SQLName="LINEITEM" xdb:SQLCollType="L
INEITEM_V"/>
23                  </xs:sequence>
24          </xs:complexType>
25          <xs:complexType name="LineItemType" xdb:SQLType="LINEITEM_T" xdb:maintainDOM="false">
26                  <xs:sequence>
27                          <xs:element name="Description" type="DescriptionType" xdb:SQLName="DESRIPTION"/>
28                          <xs:element name="Part" type="PartType" xdb:SQLName="PART"/>
29                  </xs:sequence>
30                  <xs:attribute name="ItemNumber" type="xs:integer" xdb:SQLName="ITEMNUMBER" xdb:SQLType="NUMBER"/>
31          </xs:complexType>
32          <xs:complexType name="PartType" xdb:SQLType="PART_T" xdb:maintainDOM="false">
33                  <xs:attribute name="Id" xdb:SQLName="PART_NUMBER" xdb:SQLType="VARCHAR2">
34                          <xs:simpleType>
35                                  <xs:restriction base="xs:string">
36                                          <xs:minLength value="10"/>
37                                          <xs:maxLength value="14"/>
38                                  </xs:restriction>
39                          </xs:simpleType>
40                  </xs:attribute>
41                  <xs:attribute name="Quantity" type="moneyType" xdb:SQLName="QUANTITY"/>
42                  <xs:attribute name="UnitPrice" type="quantityType" xdb:SQLName="UNITPRICE"/>
43          </xs:complexType>
44          <xs:simpleType name="ReferenceType">
45                  <xs:restriction base="xs:string">
46                          <xs:minLength value="18"/>
47                          <xs:maxLength value="30"/>
48                  </xs:restriction>
49          </xs:simpleType>
50          <xs:complexType name="ActionsType" xdb:SQLType="ACTIONS_T" xdb:maintainDOM="false">
51                  <xs:sequence>
52                          <xs:element name="Action" maxOccurs="4" xdb:SQLName="ACTION" xdb:SQLCollType="ACTION_V">
53                                  <xs:complexType xdb:SQLType="ACTION_T" xdb:maintainDOM="false">
54                                          <xs:sequence>
55                                                  <xs:element name="User" type="UserType" xdb:SQLName="ACTIONED_BY"/>
56                                                  <xs:element name="Date" type="DateType" minOccurs="0" xdb:SQLName="DATE_ACTIONED"/>
57                                          </xs:sequence>
58                                  </xs:complexType>
59                          </xs:element>
60                  </xs:sequence>
61          </xs:complexType>
62          <xs:complexType name="RejectionType" xdb:SQLType="REJECTION_T" xdb:maintainDOM="false">
63                  <xs:all>
64                          <xs:element name="User" type="UserType" minOccurs="0" xdb:SQLName="REJECTED_BY"/>
65                          <xs:element name="Date" type="DateType" minOccurs="0" xdb:SQLName="DATE_REJECTED"/>
66                          <xs:element name="Comments" type="CommentsType" minOccurs="0" xdb:SQLName="REASON_REJECTED"/>
67                  </xs:all>
68          </xs:complexType>
69          <xs:complexType name="ShippingInstructionsType" xdb:SQLType="SHIPPING_INSTRUCTIONS_T" xdb:maintainDOM="false">
70                  <xs:sequence>
71                          <xs:element name="name" type="NameType" minOccurs="0" xdb:SQLName="SHIP_TO_NAME"/>
72                          <xs:element name="address" type="AddressType" minOccurs="0" xdb:SQLName="SHIP_TO_ADDRESS"/>
73                          <xs:element name="telephone" type="TelephoneType" minOccurs="0" xdb:SQLName="SHIP_TO_PHONE"/>
74                  </xs:sequence>
75          </xs:complexType>
76          <xs:simpleType name="moneyType">
77                  <xs:restriction base="xs:decimal">
78                          <xs:fractionDigits value="2"/>
79                          <xs:totalDigits value="12"/>
80                  </xs:restriction>
81          </xs:simpleType>
82          <xs:simpleType name="quantityType">
83                  <xs:restriction base="xs:decimal">
84                          <xs:fractionDigits value="4"/>
85                          <xs:totalDigits value="8"/>
86                  </xs:restriction>
87          </xs:simpleType>
88          <xs:simpleType name="UserType">
89                  <xs:restriction base="xs:string">
90                          <xs:minLength value="1"/>
91                          <xs:maxLength value="10"/>
92                  </xs:restriction>
93          </xs:simpleType>
94          <xs:simpleType name="RequestorType">
95                  <xs:restriction base="xs:string">
96                          <xs:minLength value="0"/>
97                          <xs:maxLength value="128"/>
98                  </xs:restriction>
99          </xs:simpleType>
100          <xs:simpleType name="CostCenterType">
101                  <xs:restriction base="xs:string">
102                          <xs:minLength value="1"/>
103                          <xs:maxLength value="4"/>
104                  </xs:restriction>
105          </xs:simpleType>
106          <xs:simpleType name="VendorType">
107                  <xs:restriction base="xs:string">
108                          <xs:minLength value="0"/>
109                          <xs:maxLength value="20"/>
110                  </xs:restriction>
111          </xs:simpleType>
112          <xs:simpleType name="PurchaseOrderNumberType">
113                  <xs:restriction base="xs:integer"/>
114          </xs:simpleType>
115          <xs:simpleType name="SpecialInstructionsType">
116                  <xs:restriction base="xs:string">
117                          <xs:minLength value="0"/>
118                          <xs:maxLength value="2048"/>
119                  </xs:restriction>
120          </xs:simpleType>
121          <xs:simpleType name="NameType">
122                  <xs:restriction base="xs:string">
123                          <xs:minLength value="1"/>
124                          <xs:maxLength value="20"/>
125                  </xs:restriction>
126          </xs:simpleType>
127          <xs:simpleType name="AddressType">
128                  <xs:restriction base="xs:string">
129                          <xs:minLength value="1"/>
130                          <xs:maxLength value="256"/>
131                  </xs:restriction>
132          </xs:simpleType>
133          <xs:simpleType name="TelephoneType">
134                  <xs:restriction base="xs:string">
135                          <xs:minLength value="1"/>
136                          <xs:maxLength value="24"/>
137                  </xs:restriction>
138          </xs:simpleType>
139          <xs:simpleType name="DateType">
140                  <xs:restriction base="xs:date"/>
141          </xs:simpleType>
142          <xs:simpleType name="CommentsType">
143                  <xs:restriction base="xs:string">
144                          <xs:minLength value="1"/>
145                          <xs:maxLength value="2048"/>
146                  </xs:restriction>
147          </xs:simpleType>
148          <xs:simpleType name="DescriptionType">
149                  <xs:restriction base="xs:string">
150                          <xs:minLength value="1"/>
151                          <xs:maxLength value="256"/>
152                  </xs:restriction>
153          </xs:simpleType>
154 </xs:schema>
155 ');
156 begin
157    if (dbms_xdb.existsResource(:schemaPath)) then
158      dbms_xdb.deleteResource(:schemaPath);
159    end if;
160    res := dbms_xdb.createResource(:schemaPath,xmlSchema);
161 end;
162 /
PL/SQL procedure successfully completed.
SQL> begin
2    dbms_xmlschema.registerSchema
3    (
4      :schemaURL,
5      xdbURIType(:schemaPath).getClob(),
6      TRUE,TRUE,FALSE,FALSE
7    );
8 end;
9 /
PL/SQL procedure successfully completed.
SQL> create or replace view PURCHASEORDER_XML
2 of xmltype
3 xmlSCHEMA "http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd" Element "PurchaseOrder"
4 with object id
5 (
6    substr(extractValue(object_value,'/PurchaseOrder/Reference'),1,32)
7 )
8 as
9    select xmlElement
10           (
11             "PurchaseOrder",
12             xmlAttributes
13             (
14               'http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd' as "xsi:noNamespaceSchemaLocation",
15               'http://www.w3.org/2001/XMLSchema-instance' as "xmlns:xsi"
16             ),
17             xmlElement("Reference",p.REFERENCE),
18             xmlElement
19             (
20               "Actions",
21               ( select xmlAgg
22                        (
23                          xmlElement
24                          (
25                            "Action",
26                            xmlElement("User",ACTIONEDBY),
27                            case
28                              when DATEACTIONED is not null
29                              then xmlElement("Date",DATEACTIONED)
30                            end
31                          )
32                        )
33                   from PURCHASEORDER_ACTION a
34                  where a.REFERENCE = p.REFERENCE
35               )
36             ),
37             xmlElement
38             (
39               "Reject",
40                  xmlForest
41                  (
42                    REJECTEDBY as "User",
43                 DATEREJECTED as "Date",
44                    COMMENTS as "Comments"
45                  )
46             ),
47             xmlElement("Requestor",REQUESTER),
48             xmlElement("User",USERID),
49             xmlElement("CostCenter",COSTCENTER),
50             xmlElement
51             (
52               "ShippingInstructions",
53               xmlElement("name",SHIPTONAME),
54               xmlElement("address",ADDRESS),
55               xmlElement("telephone",PHONE)
56             ),
57             xmlElement("SpecialInstructions",SPECIALINSTRUCTIONS),
58             xmlElement
59             (
60               "LineItems",
61               ( select xmlAgg
62                        (
63                          xmlElement
64                          (
65                            "LineItem",
66                            xmlAttributes(LINENO as "ItemNumber"),
67                            xmlElement("Description",DESCRIPTION),
68                            xmlElement
69                            (
70                              "Part",
71                              xmlAttributes
72                              (
73                                UPC       as "Id",
74                                QUANTITY as "Quantity",
75                                UNITPRICE as "UnitPrice"
76                              )
77                            )
78                          )
79                        )
80                    from PURCHASEORDER_LINEITEM l
81                   where l.REFERENCE = p.REFERENCE
82               )
83             )
84           )
85      from PURCHASEORDER_TABLE p, PURCHASEORDER_REJECTION r, PURCHASEORDER_SHIPPING s
86     where r.REFERENCE = p.REFERENCE
87       and s.REFERENCE = p.REFERENCE
88 /
View created.
SQL> set long 10000 pages 0 lines 140
SQL> --
SQL> select x.object_value.extract('/*')
2    from PURCHASEORDER_XML x
3 /
<PurchaseOrder xsi:noNamespaceSchemaLocation="http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Reference>SMCCAIN-20030109123335470PDT</Reference>
<Actions>
    <Action>
      <User>SVOLLMAN</User>
    </Action>
</Actions>
<Reject/>
<Requestor>Samuel B. McCain</Requestor>
<User>SMCCAIN</User>
<CostCenter>A10</CostCenter>
<ShippingInstructions>
    <name>Samuel B. McCain</name>
    <address>800 Bridge Parkway,Redwood Shores,CA,94065,USA</address>
    <telephone>650 506 7800</telephone>
</ShippingInstructions>
<SpecialInstructions>Courier</SpecialInstructions>
<LineItems>
    <LineItem ItemNumber="1">
      <Description>Life of Brian - Monty Python's</Description>
      <Part Id="715515010320" Quantity="2" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="2">
      <Description>The Night Porter</Description>
      <Part Id="37429145227" Quantity="2" UnitPrice="29.95"/>
    </LineItem>
    <LineItem ItemNumber="3">
      <Description>Oliver Twist</Description>
      <Part Id="37429128121" Quantity="1" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="4">
      <Description>Notorious</Description>
      <Part Id="715515012720" Quantity="4" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="5">
      <Description>In the Mood for Love</Description>
      <Part Id="715515012928" Quantity="3" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="6">
      <Description>Alphaville</Description>
      <Part Id="37429130926" Quantity="2" UnitPrice="29.95"/>
    </LineItem>
    <LineItem ItemNumber="7">
      <Description>General Idi Amin Dada</Description>
      <Part Id="37429166529" Quantity="4" UnitPrice="29.95"/>
    </LineItem>
    <LineItem ItemNumber="8">
      <Description>In the Mood for Love</Description>
      <Part Id="715515012928" Quantity="3" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="9">
      <Description>Flesh for Frankenstein</Description>
      <Part Id="715515009423" Quantity="3" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="10">
      <Description>The Killer</Description>
      <Part Id="715515008976" Quantity="1" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="11">
      <Description>Ballad of a Soldier</Description>
      <Part Id="37429167922" Quantity="2" UnitPrice="29.95"/>
    </LineItem>
    <LineItem ItemNumber="12">
      <Description>Ordet</Description>
      <Part Id="37429158623" Quantity="2" UnitPrice="0"/>
    </LineItem>
</LineItems>
</PurchaseOrder>
SQL> begin
2    for x in (select object_value from PURCHASEORDER_XML) loop
3      x.object_value.schemaValidate();
4    end loop;
5 end;
6 /
PL/SQL procedure successfully completed.
SQL>

Unable to create xml from xml schema

JDeveloper 10.1.3 EA1
I am unable to create a new xml file from an xml schema when the starting root element is a complex type (but it works with a simple type). It does not matter if the xml schema is registered within JDeveloper.
Is this a bug or intended behaviour?
Error message:
''XML Document from XML Schema creation could not be competed succesfully. Make sure the source schema is valid and that you have write permissions to the output directory."
NB The xml schema is valid and I have write permissions on the specified directory.

When I do not register this (or other) schema with JDeveloper, I can create an xml document from xml schema. However, when I register this schema and then try to generate an xml document (either from the registered xsd either from a filesystem xsd) with person as starting node it fails with the mentioned error. However, when I use city as starting node it is generated successfully.
<?xml version="1.0" encoding="windows-1252" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.amis.nl/demo/hrm"
targetNamespace="http://www.amis.nl/demo/hrm"
elementFormDefault="qualified">
<xsd:element name="person">
<xsd:annotation>
<xsd:documentation>
A sample complex element
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="length" type="xsd:int"/>
<xsd:element name="weight" type="xsd:int" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="city" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
A sample simple element.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>

Create XML from oracle table if not null

Hello dear community,
I have a problem by creating an XML file in oracle and hope you could help me.
What I have is an table named "description" with three rows there:
person varchar2(50)
adress varchar2(50)
Nr number
Reading this table I am going to create an XML file like that:
Procedure Create_XML (iNr IN number, cXmlFile OUT clob) is
varPerson varchar2(50);
varAdress varchar2(50);
Begin
varPerson := ... ;
varAdress := ... ;
select
xmlserialize
content
xmlelement
"Head",
xmlelement
"Node",
xmlelement
"Line",
xmlelement("ATNAM", 'PERSON'),
xmlelement("ATWRT", PERSON),
xmlelement("ATFOR", varPerson)
xmlelement
"Line",
xmlelement("ATNAM", 'ADRESS'),
xmlelement("ATWRT", ADRESS),
xmlelement("ATFOR", varAdress)
indent
) as xml
into cXmlFile
from description
where Nr = iNr;
End Create_XML;
What I want to do, is just to take the value from the both rows "person" and "adress" and fill the xml file with additional info.
1. My first question is, if it is possible to create any kind of routine for the xmlelement "Line" instead of doing it all over and over again? How?
2. An other issue is very important to me: how can I check here if f.i. the row person is empty or not? If it is, the xmlelement "Line" with person information in it should not be created at all.
Any answer would really help me!
Thank you a lot in advance!

Hi,
Could you elaborate a little on your first question?
Are you looking for something like :
SELECT xmlquery(
'<head>
<node>
   for $i in ora:view("DESCRIPTION")/ROW[NR=$nr]/*[local-name()!="NR"]
   return element Line {
    element ATNAM {local-name($i)},
    element ATWRT {$i/text()}
</node>
</head>'
passing sys_xmlgen(1) as "nr"
returning content
FROM dual;but since you use a specific variable for each "line" type, I don't see how we can generalize the construction of the line element.

Create xml from a collection type

Similar Messages

Maybe you are looking for