Schema Parsing to create xml documents(Urgent)

Hi,
I'm new to XML and need some help for my course project. I need to parse xml schema and get the values of element name, attributes etc so that user can input values to create xml documents. Also I need to write a code that extracts the schema once the user selects schema of his choice. So its basically I need to provide dynamic interface for user to input values based on various schema.
It would be helpful if some advices me or let me know where I can proceed.
Thanx
swetha

Hello Swetha,
If you choose an XML binding technology go with JAXB 2.0. This is an industry standard included in Java since Java SE 6. Oracle offers a JAXB implementation as part of the TopLink product see the latest tech preview), and has recently open sourced it through Eclipse (Eclipse Persistence Services or EclipseLink). EclipseLink/TopLink offers features beyond what is available in standard JAXB that you may need.
TopLink object-to-XML/JAXB:
http://www.oracle.com/technology/products/ias/toplink/oxm/index.html
EclipseLink:
http://www.eclipse.org/eclipselink/
http://wiki.eclipse.org/EclipseLink
You may also consider using SDO. SDO can be viewed as a dynamic object model, the metadata can be loaded from XML Schemas (even the XML Schema for XML Schema). TopLink & EclipseLink include SDO implementations. The dynamic model is very rich in metadata which may be useful to you in creating a dynamic interface. For more information on SDO see:
http://www.osoa.org/display/Main/Service+Data+Objects+Specifications
If you are interested in the SDO approach post back, and I can provide more details.
-Blaise

Similar Messages

UCCX 8 - Dramatic change in the Create File Document step that is used by the Create XML Document step in order to read an XML file

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
For the last 5 years (and in IPCC3.x/4.x,UCCX/5.x/7.x) I've used the same basic subflow to read a XML document that contains holiday dates where the queue should be closed. I've re-used this script on 20+ client installs and it's always worked. The structure of the script allows you to pass the path and filename of the XML document as parameters to the subflow. (The document is in the repository)
I loaded this script in UCCX 8.0.2 recently and it crashed with a Java.IO error. It looked like it was trying to read the file system directly and not the repository. (In the Linux appliance model this kind of makes sense but why is the step trying to read the file system directly?)
So I open a TAC case (SR# 615243125) and TAC tells me that the method of using the Create File Document step is not supported anymore and that I should specify the filename directly in the Create XML Document step
The problem that I see (aside from having to edit all my scripts that use XML files) is that the Create XML Document step is looking for the input to be a type DOCUMENT and not a type STRING. This seems to imply that I have to hardcode the document in each script that I deploy for a customer. When it was a string it was easy to construct the full file path from parameters and pass to the subflow.
Questions to the group
#1 Am I missing something here?
#2 Do you assume that you'll be able to load a script that worked fine in UCCX 7 into UCCX 8 and that it should completely function when you're doing everything according to the step reference documentation.
#3 Cisco didn’t document this in any way that I can find.
#4 How can you use the Create XML Document step in a fashion that would let you construct the path of the file and the filename previously in the script so you could pass it to a subflow ? It would seem this functionality has been killed in UCCX 8
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
(Background)
Create File Document Step
The input filename is a STRING, could be an explicit path and filename in the repository or a variable that represents that path and string
The output of this step is a DOCUMENT to be used in the Create XML Document step
The string FILE_FullPathHolidayFiles references en_us\folderName\documentName.xml
The document was properly uploaded into the repository only, NOT trying to directly read c:\foo\blah…
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
The create XML document input can only be a type DOCUMENT

#1 Am I missing something here?
You are mixing two different issues together here.
The Create File Document step is indeed not needed or supported for creating an XML document. That is why there is a unique step; to trigger XML parsing within the MIVR subsystem.
Accessing the file system is restricted to a single folder within the VOS model (i.e. 8.0+). This folder is not backed up, replicated, or cleaned up automatically. It was intended to give developers some FS access as a temporary swap location only.
#2 Do you assume that you'll be able to load a script that
worked fine in UCCX 7 into UCCX 8 and that it should completely
function when you're doing everything according to the step reference
documentation.
Assume nothing; read the documentation and attend one of the dozens of partner training sessions that CCBU put on advising of the upcoming changes.
#3 Cisco didn’t document this in any way that I can find.
You're right, I guess, on the Create File vs. XML Document step. AFAIK Cisco never wrote a notice into the Step Reference Guide explicitly stating that you cannot use the Create File Document although the documentation seemed pretty clear to me without it. File system restrictions are documented in the 8.0 release notes.
Scripting and Development Series: Volume 2, Editor Step ReferenceUse the Create XML Document step to create a logical document that maps a document to another document variable (where the document has already been pre-parsed as an XML document and is ready to be accessed by the Get XML Document Data step).Use this step before the Get XML Document Data step to obtain data from a document formatted using the Extensible Markup Language (XML).
#4 How can you use the Create XML Document step in a fashion that would
let you construct the path of the file and the filename previously in
the script so you could pass it to a subflow ? It would seem this functionality has been killed in UCCX 8
No it hasn't; just concatinate a string to build the Source Document parameter the step needs. Example: "DOC[" + myFilePath + "]"

Error in tutorial: Could not create XML document carrying AQ Headers

Hi,
We try to run the AQOutboundCorrelation tutorial. After running the enqueue_reply.sql script the message was placed from the request to the reply queue and read by the AQ inbound adapter.
Nothing happened in the flow. The following error occured in the domain log:
Could not create XML document carrying AQ Headers
Please help!!
See log messages below
<2007-01-18 13:58:59,187> <DEBUG> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_addPrimitive: field = PAYLOAD, value = Hallo
<2007-01-18 13:58:59,187> <DEBUG> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_addPrimitive: field = RESULT, value = request received
<2007-01-18 13:58:59,187> <DEBUG> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_getAsXML message:<<<<<<<
<?xml version = '1.0' standalone = 'yes'?>
<CORRELATIONREPLY_TYPE xmlns="http://xmlns.oracle.com/xdb/ANDRE">
<PAYLOAD xmlns="">Hallo</PAYLOAD>
<RESULT xmlns="">request received</RESULT>
</CORRELATIONREPLY_TYPE>
>>>>>>>>
<2007-01-18 13:58:59,187> <DEBUG> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_readMessage: aqHeader = oracle.xml.parser.v2.XMLDocument@eabad
<2007-01-18 13:58:59,187> <DEBUG> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_readMessage:Header<<<<<<<
<?xml version = '1.0' standalone = 'yes'?>
<Header xmlns="http://xmlns.oracle.com/pcbpel/adapter/aq/inbound/">
<MessageId>CA714367FA1B4BB3B2AC0211C9ECF2DB</MessageId>
<Priority>1</Priority>
<Correlation>209EE57CB6AC4B2FA2034C6FA58AD24B</Correlation>
<Attempts>0</Attempts>
<EnqueueTime>2007-01-18T13:58:59.000+01:00</EnqueueTime>
<OrigMessageId></OrigMessageId>
</Header>
>>>>>>>>
<2007-01-18 13:58:59,187> <ERROR> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_ReadMessage: Could not create XML document carrying AQ Headers: [Ljava.lang.StackTraceElement;@12916fe
<2007-01-18 13:58:59,187> <ERROR> <default.collaxa.cube.activation> <AQ Adapter::Inbound>
java.lang.NullPointerException
     at java.lang.String.<init>(String.java:479)
     at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:573)
     at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:183)
     at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
     at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:272)
     at java.lang.Thread.run(Thread.java:595)
Message was edited by:
rverbeea1

Sorry for not mentioning the product versions:
The bpel process was build and deployed with Jdeveloper Studio edition version 10.1.3.1.0.3984 on a Bpel server/Application Server with version 10.1.3.1 (NT).

Heap space error while creating XML document from Resultset

I am getting Heap space error while creating XML document from Resultset.
It was working fine from small result set object but when the size of resultset was more than 25,000, heap space error
I am already using -Xms32m -Xmx1024m
Is there a way to directly write to xml file from resultset instead of creating the whole document first and then writing it to file? Code examples please?
here is my code:
stmt = conn.prepareStatement(sql);
result = stmt.executeQuery();
result.setFetchSize(999);
Document doc = JDBCUtil.toDocument(result, Application.BANK_ID, interfaceType, Application.VERSION);
JDBCUtil.write(doc, fileName);
public static Document toDocument(ResultSet rs, String bankId, String interfaceFileType, String version)
    throws ParserConfigurationException, SQLException {
        DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
        DocumentBuilder builder = factory.newDocumentBuilder();
        Document doc = builder.newDocument();
        Element results = doc.createElement("sims");
        results.setAttribute("bank", bankId);
        results.setAttribute("record_type", "HEADER");
        results.setAttribute("file_type", interfaceFileType);
        results.setAttribute("version", version);
        doc.appendChild(results);
        ResultSetMetaData rsmd = rs.getMetaData();
        int colCount = rsmd.getColumnCount();
        String columnName="";
        Object value;
        while (rs.next()) {
            Element row = doc.createElement("rec");
            results.appendChild(row);
            for (int i = 1; i <= colCount; i++) {
                columnName = rsmd.getColumnLabel(i);
                value = rs.getObject(i);
                Element node = doc.createElement(columnName);
                if(value != null)
                    node.appendChild(doc.createTextNode(value.toString()));
                else
                    node.appendChild(doc.createTextNode(""));
                row.appendChild(node);
        return doc;
public static void write(Document document, String filename) {
        //long start = System.currentTimeMillis();
        // lets write to a file
        OutputFormat format = new OutputFormat(document); // Serialize DOM
        format.setIndent(2);
        format.setLineSeparator(System.getProperty("line.separator"));
        format.setLineWidth(80);
        try {
            FileWriter writer = new FileWriter(filename);
            BufferedWriter buf = new BufferedWriter(writer);
            XMLSerializer FileSerial = new XMLSerializer(writer, format);
            FileSerial.asDOMSerializer(); // As a DOM Serializer
            FileSerial.serialize(document);
            writer.close();
        } catch (IOException ioe) {
            ioe.printStackTrace();
        //long end = System.currentTimeMillis();
        //System.err.println("W3C File write time :" + (end - start) + " " + filename);
    }

you can increase your heap size..... try setting this as your environment variable.....
variable: JAVA_OPTS
value: -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m

RE: (forte-users) XML Parser - Reading an XML document intothe Document

Hi Laks
Here is an example of converting a XML doc to a DOM object.
The method is ParseXML(pXMLString:TextData, pListType:CSAListInterface).
Hope this helps.
Argyris Simakis
Corporate Services Applications ITB
Sydney AUSTRALIA
-----Original Message-----
From: Narayanan, Lakshmi [mailto:lnarayanoxhp.com]
Sent: Thursday, April 06, 2000 8:31 AM
To: 'kamranaminyahoo.com'
Subject: (forte-users) XML Parser - Reading an XML document into the
Document Object
Importance: High
Hi guys,
I have been trying to read an XML file and feed it into the XMLParser.
I have read about the DOM API, and i can work with the DOM API in java
scripts. How
will i play with it in TOOL implementation of DOM API. Can anyone guide me
in this
process.
Thanks for your help.
Laks
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

Hi Laks
Here is an example of converting a XML doc to a DOM object.
The method is ParseXML(pXMLString:TextData, pListType:CSAListInterface).
Hope this helps.
Argyris Simakis
Corporate Services Applications ITB
Sydney AUSTRALIA
-----Original Message-----
From: Narayanan, Lakshmi [mailto:lnarayanoxhp.com]
Sent: Thursday, April 06, 2000 8:31 AM
To: 'kamranaminyahoo.com'
Subject: (forte-users) XML Parser - Reading an XML document into the
Document Object
Importance: High
Hi guys,
I have been trying to read an XML file and feed it into the XMLParser.
I have read about the DOM API, and i can work with the DOM API in java
scripts. How
will i play with it in TOOL implementation of DOM API. Can anyone guide me
in this
process.
Thanks for your help.
Laks
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

RE: (forte-users) XML Parser - Reading an XML document intothe D ocumen

Hi Simakis,
Your attachments explained the exact start i was looking for.
Thanks a lot for sharing.
Thanks
Laks
-----Original Message-----
From: Simakis, Argyris [mailto:Argyris.Simakisdet.nsw.edu.au]
Sent: Thursday, April 06, 2000 12:35 AM
To: 'Narayanan, Lakshmi'
Cc: 'kamranaminyahoo.com'
Subject: RE: (forte-users) XML Parser - Reading an XML document into the
D ocument Object
Hi Laks
Here is an example of converting a XML doc to a DOM object.
The method is ParseXML(pXMLString:TextData, pListType:CSAListInterface).
Hope this helps.
Argyris Simakis
Corporate Services Applications ITB
Sydney AUSTRALIA
-----Original Message-----
From: Narayanan, Lakshmi [mailto:lnarayanoxhp.com]
Sent: Thursday, April 06, 2000 8:31 AM
To: 'kamranaminyahoo.com'
Subject: (forte-users) XML Parser - Reading an XML document into the
Document Object
Importance: High
Hi guys,
I have been trying to read an XML file and feed it into the XMLParser.
I have read about the DOM API, and i can work with the DOM API in java
scripts. How
will i play with it in TOOL implementation of DOM API. Can anyone guide me
in this
process.
Thanks for your help.
Laks
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

Hi Simakis,
Your attachments explained the exact start i was looking for.
Thanks a lot for sharing.
Thanks
Laks
-----Original Message-----
From: Simakis, Argyris [mailto:Argyris.Simakisdet.nsw.edu.au]
Sent: Thursday, April 06, 2000 12:35 AM
To: 'Narayanan, Lakshmi'
Cc: 'kamranaminyahoo.com'
Subject: RE: (forte-users) XML Parser - Reading an XML document into the
D ocument Object
Hi Laks
Here is an example of converting a XML doc to a DOM object.
The method is ParseXML(pXMLString:TextData, pListType:CSAListInterface).
Hope this helps.
Argyris Simakis
Corporate Services Applications ITB
Sydney AUSTRALIA
-----Original Message-----
From: Narayanan, Lakshmi [mailto:lnarayanoxhp.com]
Sent: Thursday, April 06, 2000 8:31 AM
To: 'kamranaminyahoo.com'
Subject: (forte-users) XML Parser - Reading an XML document into the
Document Object
Importance: High
Hi guys,
I have been trying to read an XML file and feed it into the XMLParser.
I have read about the DOM API, and i can work with the DOM API in java
scripts. How
will i play with it in TOOL implementation of DOM API. Can anyone guide me
in this
process.
Thanks for your help.
Laks
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

Help in creating XML documents in ABAP using XI in new version ECC6.0

Hello All:
I am pretty comfortable with XML and XSLT but new to XI. Is there a way of creating XML documents in ABAP using XI in new version ECC6.0? Please provide me with any links or any information you may have. All the answers will be rewarded.
Thanks.
Mithun

hi,
U cant create XML data in ABAP.
to send the data to the XI, u have to use the IDOC or RFC FM, from there IDOC or RFC adapters will read the data in the same format and these adapters will convert the data in to XML .Bcoz XI understand only XML data.
from there XI will process and route them to Destination, by using anthor adapter.
here u can use file adapter if u want data in file foramat from the IDOC or RFC .
So XI is the integration tool only.
reward points if helpful
ragards
sreeni

AQ Adapter error: Could not create XML document carrying AQ Headers

I'm having problem with the AQ adapter (ADT) sample that comes with the SOA 10g install.
I am running 10.1.3.4 on XP, using Oracle XE.
I can use the sample sql script to enque and deque. However, when I deploy the sample ADT (BPEL project), I see errors in the opmn log. The BPEL instance is not even created.
I see another post with similar question, Re: Debugging BPEL when using Oracle AQ but no answer.
Any help is greatly appreciated. Thx!
----------------- err log --------------
<2009-07-15 00:04:31,656> <INFO> <collaxa> <ServerManager::loadProcesses> Done loading processes for all domains
<2009-07-15 00:04:32,031> <INFO> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_ctor: Initialized MessageReader for queue CUSTOMER_IN_QUEUE, consumer = null)
<2009-07-15 00:12:15,984> <ERROR> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_ReadMessage: Could not create XML document carrying AQ Headers: [Ljava.lang.StackTraceElement;@e7af3a
<2009-07-15 00:12:15,984> <ERROR> <default.collaxa.cube.activation> <AQ Adapter::Inbound>
java.lang.Exception: java.lang.NullPointerException
     at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:750)
     at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:261)
     at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
     at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:280)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
     at oracle.oc4j.sql.proxy.StatementBCELProxy.oc4j_releaseToCache(StatementBCELProxy.java:67)
     at oracle.oc4j.sql.proxy.StatementBCELProxy.oc4j_releaseTarget(StatementBCELProxy.java:79)
     at oracle.oc4j.sql.proxy.SQLBCELProxy.oc4j_close(SQLBCELProxy.java:95)
     at oracle.oc4j.sql.proxy.StatementBCELProxy.close(StatementBCELProxy.java:92)
     at oracle.AQ.AQOracleQueue.destroyStmt(AQOracleQueue.java:3099)
     at oracle.AQ.AQOracleQueue.dequeue(AQOracleQueue.java:1793)
     at oracle.AQ.AQOracleQueue.dequeue(AQOracleQueue.java:1307)
     at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:485)
     ... 4 more
<2009-07-15 00:12:16,203> <FATAL> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Uncaught exception oracle.as.j2ee.transaction.tpc.ProtocolErrorWithNotification in JCA-work-instance:AQ Adapter-0 - cause: Branch [oracle.oc4j.sql.xa.EmulatedXAResource@14d9865, Xid( Global Id 34.5f.1e.a8.ff.ff.ff.ff.cd.b9.38.7d.22.01.00.00.7a.02.00.00.00.00.00.00, Format Id 1330790740, Branch Id 7c.e5.55.76.00.00.00.00.00.00.00.00.00.00.00.01), oracle.oc4j.sql.xa.EmulatedXAResource@14d9865, state={PREPARED}, exception error code=] in transaction Global Transaction Xid( Global Id 34.5f.1e.a8.ff.ff.ff.ff.cd.b9.38.7d.22.01.00.00.7a.02.00.00.00.00.00.00, Format Id 1330790740), type=orabpel, state=COMMITTING, time in completion or recovering=0)
....

thanks for the reply. I did look into that post, and couldn't found where to set that option either.
However, my PC was rebooted a few times today (I didn't change anything with BPEL), and I just re-ran the test now, that problem disappeared! It is working fine now.

Could not create XML document carrying AQ Headers

Hi gurus,
I’m trying to run the "Simple_XMLType_Payload" sample, and I have successfully deploy it on Oracle BPEL v10.1.3.1.0 , and after en-queue into the XMLType_Payload_In queue the recorded has been de-queued successfully, however there no instance for the BPEL has been created on the BPEL Console moreover there is no recorded inserted in XMLType_Payload_Out queue.
After investigating the OC4j_SOA log file, I found the following error
11/03/29 16:32:45 Confluent Monitor component started
11/03/29 16:32:45 Oracle Containers for J2EE 10g (10.1.3.1.0) initialized
11/03/29 16:52:28 java.lang.ClassCastException: oracle.xdb.XMLType
11/03/29 16:52:28      at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:448)
11/03/29 16:52:28      at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:189)
11/03/29 16:52:28      at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
11/03/29 16:52:28      at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:272)
11/03/29 16:52:28      at java.lang.Thread.run(Thread.java:595)
<2011-03-29 16:52:28,082> <ERROR> <defualt.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_ReadMessage: Could not create XML document carrying AQ Headers: [Ljava.lang.StackTraceElement;@748771
<2011-03-29 16:52:28,089> <ERROR> <defualt.collaxa.cube.activation> <AQ Adapter::Inbound>
java.lang.ClassCastException: oracle.xdb.XMLType
     at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:448)
     at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:189)
     at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
     at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:272)
     at java.lang.Thread.run(Thread.java:595)

But I have tried it on another server that also has 10.1.3.1 version but the OS version is HP-UX B.11.23 U ia64 , and it woks fine, however I’m still has the same issue on the original server that has OS version HP-UX B.11.31 U ia64 ?
Edited by: user11096490 on Apr 4, 2011 11:06 AM

Get SOAP Cannot Create XML Document reader error with Outlook integration?

Hi,
We installed Outlook Email Integration on a windows XP / Office 2007 machine and it installed OK. However when we click the "Add to CRM On Demand" button and try to login we get the following error message when we click the 'Sign In" button
"SOAP: Cannot create XML document reader"
Has anyone come across this? Are there any pre-requisites for using this add-in? e.g. Service Packs, .NET framework etc?
Cheers

It may not be the case...but pls. check if MS Word is defined as editing tool for email.. It should not be.
ANotnio
BExpert, Brazil

Dynamically creating XML document in XMLBeans via Schema

Hello,
Does anyone know if XMLBeans has the capability of creating a default XML document based on a schema, and if so give a few pointers on how to do this.
Cheers,
SB

Check out these links:
http://www.devx.com/xml/Article/17495/1954?pf=true
http://www.javaworld.com/javaworld/jw-11-1999/jw-11-beans_p.html
http://xmlbeans.apache.org/documentation/tutorial_getstarted.html

How to create XML document in Java from scratch ?

I've downloaded the package generated for my schema.
Now I'm trying to create a XML Document using the interfaces generated and the
xmlbeans package. In documentation, all samples start with a call to XmlLoader.load(xmlinput).
In my case I've no xmlinput, I've only java parameters and i need to produce an
XML document.
Could you provide a sample code please ?
Thanks in advance.

It looks like you only need to use the xmlText() method from the root of any node
you want to print out to a file. I used a PrintStream() class and then used the
ps.print(vpDetails.xmlText()); to save to a file.
Hope this helps.
Jerald
"Eric Vasilik" <[email protected]> wrote:
>
To create a new, untyped document:
XmlObject x = XmlLoader.newInstance();
To create a new, typed document:
Map options = new HashMap(
XmlOptions.DOCUMENT_TYPE,
CustomerDocument.type );
CustomerDocument cd = (CustomerDocument) =
XmlLoader.newInstance( options );
I have changes pending which will alow you to do this more easily:
CustomerDocument cd = CustomerDocument.Factory.newInstance();
- Eric
"Pascal Fuget" <[email protected]> wrote:
I've downloaded the package generated for my schema.
Now I'm trying to create a XML Document using the interfaces generated
and the
xmlbeans package. In documentation, all samples start with a call to
XmlLoader.load(xmlinput).
In my case I've no xmlinput, I've only java parameters and i need to
produce an
XML document.
Could you provide a sample code please ?
Thanks in advance.

Create xml document with xsd

Hi,
i'm new at this, so i need some help. I am developing web service that interacts with user over SOAP. User has to send xsd and web service has to create or update xml whitch is something like database. Is this posible?
Thanx,
Alan.

With XMLBeans an XML document may be generated from a schema.
Refer to section
Creating New XML Instances from Schema
http://xmlbeans.apache.org/docs/2.0.0/guide/conGettingStartedwithXMLBeans.html

Use JAXP for creating XML document

Hi,
I have used JAXP to create a XML docuemnt. But when I use Jaxp to parse it, it returns parsing error ''null''.
I open the XML document in XMLspy and save again, then it can be parsed.
Any suggestion for that? Thanks a lot.

Are there any differences between the version created with jaxp and the one with xmlspy? are you using the validating parser? if you aren't you might be having trouble with white space. just a guess.

Parse and output XML document while preserving attribute order

QUESTION: How can I take in an element with attributes from an XML and output the same element and attributes while preserving the order of those attributes?
The following code will parse and XML document and generate (practically) unchanged output. However, all attributes are ordered a-z
Example: The following element
<work_item_type work_item_db_site="0000000000000000" work_item_db_id="0" work_item_type_code="3" user_tag_ident="Step" name="Work Step" gmt_last_updated="2008-12-31T18:00:00.000000000" last_upd_db_site="0000000000000000" last_upd_db_id="0" rstat_type_code="1">
</work_item_type>is output as:
<work_item_type gmt_last_updated="2008-12-31T18:00:00.000000000" last_upd_db_id="0" last_upd_db_site="0000000000000000" name="Work Step" rstat_type_code="1" user_tag_ident="Step" work_item_db_id="0" work_item_db_site="0000000000000000" work_item_type_code="3">
</work_item_type>As you may notice, there is no difference in these besides order of the attributes!
I am convened that the problem is not in the stylesheet.xslt but if you are not then it is posted bellow.
Please, someone help me out with this! I have a feeling the solution is simple
The following take the XML from source.xml and outputs it to DEST_filename with attributes in a-z order
Code:
private void OutputFile(String DEST_filename, String style_filename){
     //StreamSource stylesheet = new StreamSource(style_filename);
     try{
          File dest_file = new File(DEST_filename);
          if(!dest_file.exists())
              dest_file.createNewFile();
          TransformerFactory tranFactory = TransformerFactory.newInstance();
          Transformer aTransformer = tranFactory.newTransformer();
          aTransformer.setOutputProperty(OutputKeys.ENCODING, "UTF-8");
          Source src = new DOMSource("source.xml");
          Result dest = new StreamResult(dest_file);
          aTransformer.transform(src, dest);
          System.out.println("Finished");
     catch(Exception e){
          System.err.print(e);
          System.exit(-1);
    }

You can't. The reason is, the XML Recommendation explicitly says the order of attributes is not significant. Therefore conforming XML serializers won't treat it as if it were significant.
If you have an environment where you think that the order of attributes is significant, your first step should be to reconsider. Possibly it isn't really significant and you are over-reaching in some way. Or possibly someone writing requirements is ignorant of this fact and the requirement can be discarded.
Or possibly your output is being given to somebody else who has a defective parser which expects the attributes to be in a particular order. You could quote the XML Recommendation to those people but often XML bozos are resistant to change. If you're stuck writing for that parser then you'll have to apply some non-XML processing to your output to fix it up on their behalf.

Schema Parsing to create xml documents(Urgent)

Similar Messages

Maybe you are looking for