Xmldoc.createSchemaBasedXML validation only validates against root element?

I'm attempting to validate an XML document against a registered schema using xmldoc.createSchemaBasedXML.
The only time I can get the validation to fail is if the top level element is incorrect.
Otherwise it always seems to validate OK, no matter what errors are in the file.
This is a slimmed down version of the XML output as it should appear:
<students>
<student id="10257">
<personNumber>10302</personNumber>
</student>
</students>
If I pass this to xmldoc.createSchemaBasedXML it does not error, which is correct.
If I pass this:
<monkeys>
<student id="10257">
<personNumber>10302</personNumber>
</student>
</monkeys>
it fails with the error:
ORA-31043: Element 'monkeys' not globally defined in schema 'http://www.ox.ac.uk/studentDataFeed'
This is also correct.
However, if I pass this:
<students>
<rabbit id="10257">
<personNumber>10302</personNumber>
</rabbit>
</students>
or this:
<students>
<student id="10257">
<hedgehogNumber>10302</hedgehogNumber>
</student>
</students>
it does not return any error.
Am I misunderstanding the type of validation that will take place when we invoke this method? Or have I possible registered my schema incorrectly.
Thanks for any suggestions
Ben

Where does one lookup bugs/issues, mind that I am not an Oracle employee or customer ?
Maybe if it's not getting adressed/fixed in the near future, people can avoid triggering this bug by knowing what causes it. I'd appreciate at least getting to the description of the problem so that I can re-format documents/schema accordingly and still be able to use XDK with schema validation capability.
Regards,
Amir

Similar Messages

OrgChart Hierarchy only shows root element

Hi experts
In OrgChart module, when position hierachy is accessed, only shows the
root element, not hierachy structure of postion elements.
When click this element, no data was showed in details pannel.
Any idea?

Hi Savier,
Do you maintain S A 002 S relationships in SAP? If not then you will not get the Position Hierarchy because the Positions do not have a relationship between themselves. In Staged you have to derive the relationships and in Live you will either have to maintain the relationships or use an FM to derive the relationships and add it to an Evaluation Path. Otherwise you will have to disable the feature.
Good luck!
Luke

Parsing xml file error: Document root element is missing.

Hi,
When I try to parse an xml file with SAX parser, the SAXParseException message I got is: "Document root element is missing." Anybody knows what it is? How should I fix it? Thanks a lot in advance!
J.H.

An XML document has only a single root element. So after the XML header, your document must look something like this:
<tag>
</tag>
If you have more than one element like this, for example:
<tag>
</tag>
<anothertag>
</anothertag>
then you don't have a root element and your parser will give the message you referred to.

Problem to validate XML document if the type of root element is abstract

I have the following XML document:
<?xml version="1.0" encoding="UTF-8"?>
<ct013/>
It corresponds to the following XSD Schema:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="ct013" type="foo"/>
     <xs:complexType abstract="true" name="foo"/>
     <xs:complexType name="fixedType">
          <xs:complexContent>
               <xs:restriction base="foo"/>
          </xs:complexContent>
     </xs:complexType>
</xs:schema>
Please take attention to the fact that the type of root element of that BDD is abstract.
XML Schema provides a mechanism to force substitution for a particular element or type. When an element or type is declared to be "abstract", it cannot be used in an instance document. When an element is declared to be abstract, a member of that element's substitution group must appear in the instance document. When an element's corresponding type definition is declared as abstract, all instances of that element must use xsi:type to indicate a derived type that is not abstract.
Declaring an element as abstract requires the use of a substitution group. Declaring a type as abstract simply requires the use of a type derived from it (and identified by the xsi:type attribute) in the instance document.
For more information of using abstract types please see chapter 4.7 Abstract Elements and Types of XML Schema Part 0: Primer Second (http://www.w3.org/TR/xmlschema-0/#abstract).
In this case there is Oracle bug when I try to validate this XML document using Oracle XDK:
String validate(String xml, String schema)
throws XSDException, XMLParseException, SAXException, IOException
System.setPropert("oracle.xml.parser.debugmode", "true");
XSDValidator xsdValidator = new XSDValidator();
XMLError xmlError = new XMLError();
xmlError.setErrorHandler(new DocErrorHandler());
XMLDocument xmlDocument = parseXMLDocument(xml);
XMLDocument schemaXMLDocument = parseXMLDocument(schema);
XMLSchema xmlSchema = (XMLSchema) new XSDBuilder().build(schemaXMLDocument, null);
xsdValidator.setError(xmlError);
xsdValidator.setSchema(xmlSchema);
xsdValidator.validate(xmlDocument);
return getValidationError(xsdValidator);
I get the following error:
Can't find resource for bundle oracle.xml.mesg.XMLResourceBundle, key XSD-2046.
I tried to validate this XML document using two other libraries - XSD Schema Validator (http://apps.gotdotnet.com/xmltools/xsdvalidator/Default.aspx) and xsdvalid-29 (http://www.w3.org/XML/Schema#XSDValid). Both libraries pointed me on the error that the type of root element is abstract and it cannot be used for doing validation.
I think that Oracle should return me explaining message but not to throw exception.
Am I right? Is there really Oracle bug or I miss something?
Any help, hits, advices would be gratfully apriciated.

Define Element1 as follows:
<xs:element name="Element1">
<xs:complexType>
<xs:complexContent>
<xs:restriction base="xs:string"/>
</xs:complexContent>
</xs:complexType>
</xs:element>
Does the XML document get validated if the element is specified as
<Element1></Element1>

Go Daddy UCC Certificate: "ExRCA can only validate the certificate chain using the Root Certificate Update functionality from Windows Update"

Hello,
I have this issue regarding certificate chains while performing Outlook Anywhere connectivity test
by Microsoft Remote Connectivity Analyzer:
"ExRCA can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled."
Note: even if I got the error, Outlook Anywhere and
ActiveSync services work fine.
Environment:
- Exchange 2007 with SP3
- Go Daddy Multiple Domains UCC certificate (up to 5 Subject Alternative Names)
I already read and followed instructions on this TechNet post
Can I safely ignore this warning about the SSL cert? Using GoDaddy UCC cert but it is a little bit different by this case.
So after an investigation I understand the issue above is related to SSL certificate
Certification Path (see screenshots below).
NO ERRORS on ExRCA checking
Go Daddy Secure Certification Authority is under Intermediate Certification Authorities
repository
Go Daddy Class 2 Certification Authority is under Intermediate Certification Authorities
repository
Starfield Technologies (http://www.valicert.com)
is under Trusted Root Certification Authorities repository
ERROR on ExRCA checking
Go Daddy Secure Certification Authority is under Intermediate Certification Authorities
repository
Go Daddy Class 2 Certification Authority is under Trusted Root Certification Authorities
repository
Can you add some useful information ?
I'm opening a support ticket at Go Daddy; I hope they could me some positive feedbacks.
Regards,
Luca Fabbri
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

Strange I have a feeling the exrca tool can't validate the godaddy class2 root authority due some older compability and wants to use the older original root authority valicert owned godaddy. Or when the exrca tool is validating the root CA it only has the
goaddy class2 root ca that was issued by valicert and not the standalone cert when doing the comparision. I sent the question to MS and will let you know when I hear back.
You can get rid of it
https://certs.godaddy.com/anonymous/repository.seam
Download the cert
◦gd_cross_intermediate.crt
Then import it into the trusted root cert authority on your CAS boxes. Then you need to delete the other godaddy class2 root authority. Make sure you see the one you imported both will be named goaddy class2 root authority but one will be issued by valicert.
Re-run the test and it will go away, I also saw the error with my domain as well using godaddy and got rid of it by using the new cert authority.
James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Validate xml with complextype schema without root element!

Hi All!
I have a problem that. I want to validate a xml data of complextype but the schema i want to validate is[b] not have root element.
For example:
The schema like that
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="www.thachpn.test" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="www.thachpn.test" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <xs:complexType name="Name">
          <xs:sequence>
               <xs:element name="FirstName" type="xs:string"/>
               <xs:element name="LastName" type="xs:string"/>
          </xs:sequence>
     </xs:complexType>
</xs:schema>
and the xml data i want to validate like this
<?xml version="1.0" encoding="UTF-8"?>
<Name xmlns="www.thachpn.test" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <FirstName>Pham</FirstName>
     <LastName>Thach</LastName>
</Name>
My Algorithm is like that:
I create a complextype object by above schema
then i create new element with given name and namespace
after that i use schema of this element to validate xml data.
I use xmlparserv2 lib of oracle
But i can not find how to create complextype from schema or create element with have complextype.
Please help me.
Thanks a lot!

<?xml version="1.0" encoding="UTF-8"?>
Modify the schema.
Add a root element.
<xs:schema targetNamespace="www.thachpn.test" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="www.thachpn.test" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xsd:element name="Name" type="Name"/>
<xs:complexType name="Name">
<xs:sequence>
<xs:element name="FirstName" type="xs:string"/>
<xs:element name="LastName" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:schema>

Declaring namespaces ONLY on root element during serialization

I'm using JAXP 1.3 and I'd like to be able to serialize a document so that the namespace declarations are only specified once on the root element and not repeated throughout the document.
I'm working on a journal publication system and the request came from our users (i.e., editors) who say the repeated declarations are distracting when editing the XML. They are using an XML editor (Arbortext), but when they have the view set to display tags all the namespace declarations really clutters up the screen. In particular, we use the MathML namespace:
<m:math overflow="scroll" xmlns:m="http://www.w3.org/1998/Math/MathML">
Can this be done?
Thanks,
Jeff Bailey

It's just declared on on the root element on the input file.
I just tried what you suggested and it worked great. The mathml namespace is only declared on the root element in my output file now.
Odd that there's a difference between the two methods. For posterity, here's the code I used to serialize the XML:
TransformerFactory transformerFactory = TransformerFactory
.newInstance();
Transformer transformer = transformerFactory.newTransformer();
transformer.setOutputProperty(OutputKeys.METHOD, "xml");
transformer.setOutputProperty(OutputKeys.ENCODING, "US-ASCII");
transformer.setOutputProperty(OutputKeys.DOCTYPE_PUBLIC,
doc.getDoctype().getPublicId());
transformer.setOutputProperty(OutputKeys.DOCTYPE_SYSTEM,
doc.getDoctype().getSystemId());
OutputStream outputStream = new FileOutputStream(new File(
"C:\\temp\\foo.xml"));
transformer.transform(new DOMSource(doc),
new StreamResult(outputStream));
Thanks very much for your help.
Jeff

XML Data Source: does not seem to validate against XSD

I setup XML data source using the example "b-c.xml" and "b-c.xsd"; I changed the
root element of "b-c.xml" from "<db>" to "<Customers>"; but Liquid Data does not
seem to care or validate the instance document against the XSD.
Is this a known bug? It's something very basic and obvious!

LD does indeed catch and report the mis-match at run-time as shown in the exception
below.
It does not valid the XML file against the schema at configuration time, only
at run-time. Hence Step 8 here - http://edocs/liquiddata/docs81/admin/xml.html#1035818
But beware - in some (most) cases LD does not do validation against the schema
for performance reasons. If the schema does not match you will simply get empty
results.
- Mike
java.rmi.RemoteException: Query Execution Error (Run Time) 1-2-3-24: Cannot process
XML file source XM-BB-C. (com.enosysmarkets.xqdm.translators.XqdmTranslatorException:
Invalid root element name: 'CUSTOMERS'. Expected: 'db')
"David Song" <[email protected]> wrote:
>
I setup XML data source using the example "b-c.xml" and "b-c.xsd"; I
changed the
root element of "b-c.xml" from "<db>" to "<Customers>"; but Liquid Data
does not
seem to care or validate the instance document against the XSD.
Is this a known bug? It's something very basic and obvious!

Root element is missing - Response from a WCF service - WCF-Custom adapter

hi BizTalk experts,
In the production environment, as soon as the response is getting subscribed by the orchestration, the orchestration instance is getting suspended and the error that shows up in console is
"Root element is missing".
I have checked the actual response message in the console it is a well formed xml. This is happening only for a few responses from the WCF services. A majority of them are getting processed successfully. I have tried getting the parsing the response in a
pipeline (using custom pipeline component, the production one uses xml receive) and pass it to the orchestration, but it fails giving the same error.
Thanks in advance.

Do you have any mapping done on the response message from the WCF service . ?
If so Better to copy the suspended message coming from the WCF service and validate against the custom response Schema you have created.
Note : You can try running fiddler tool to check the response from from the web service incase of failure.
Also try logging the message in the event viewer or any debug tool.
Thanks
Abhishek

Root element required error in syndication

Hi,
We have added few new fields into the main table. Now accordingly we need to update the Oubound map to include these new fields. I have created a new XSD file having these new fields. But when I try to use this in syndicator to update, it throws me an error back saying "Root element required". I checked in SDN but couldnt find enough clues.
Any pointers will be highly appreciated.
Regards,
Ponraj M

Hello,
There are few possible root causes to this error appearing in MDM Syndicator:
1. This error indicates that the XSD is not valid as there is no declaration of the root element.
If you try to validate this XSD in XMLspy you will receive a similar error.
2. The XSD declares the root element but it does not appear in the XML.
If you validate the XML against the XSD in XMLspy you will receive a similar error.
3. An illegal character in the XSD root element declaration makes it impossible for Syndicator to detect it.
Please check these possible causes.
Best regards,
Hedda Cohen.

Hyperion Business Rule Error: Cannot retrieve connected root element for

Hi,
I am trying to open a business rule in EAS and I am recieving the following error: Cannot retrieve connected root element for Planning/Servername/Application/Database.
I am able to connect to the application via Planning Web, but I am recieving this message when I am trying to open the business rule in eas.
hoping if someone has come across this issue before and has been able to successfully fix it.

Hi,
I have 2 BRs, one is with RTP and another without RTP (basically a clacscript as BR).
I don't have any issue with the BR without RTP.
When I try to validate BR withRTP, validation is failing with
Unable to run or validate this rule (ConsolidateTestRTP) against the following location: Planning/servername/appname/dbname for user abcd.
Detail:Exception occurred. Please check your log file for details.
2009-04-09 12:35:58,803 WARN AWT-EventQueue-0 com.hyperion.hbr.core.MetadataManagerServerRemote - Cannot retrieve connected root element for Planning/servername/appname/dbname
Restarted RMI,Planning,EAS services. Logged into planning first and then to EAS. Still getting error
2009-04-09 12:41:39,881 FATAL AWT-EventQueue-0 com.hyperion.hbr.client.LauncherWindow - Exception:
With thought of may be the syntax of RTPs in BR changed, deleted RTP in the code but still BR has RTP (I mean BR has RTP and is not used in calculations), still getting error during validation. I can create new BRs and associate to outline.
Thanks

Task.toXML() creates xml that does not validate against WorklistTask.xsd

I am using the worklist API and I am using the toXML() function provided in the Task object to serialize my Task info to XML. It produces XML that looks alot like a "task" Element. But, it does not validate against the WorkflowTask.xsd schema. What is even more odd is that XML looks different than the xml I see when I look at the data in the BPEL Console.
For example, the first XML document below is from Task.toXML. notice that it's first child element is taskId. According to the xsd, that is not valid. The second xml document in this post is from the console. it appears to be valid.
Am I doing something wrong or should I just not expect the worklist api to produce valid xml? (correction: should I not expect the worklist api to xml that validates?)
<task xmlns="http://xmlns.oracle.com/pcbpel/taskservice/task"><taskId>0D7B97F1B138EE21E04017AC2B194357</taskId><title>Payment not posted by payee</title><isGroup>true</isGroup><acquiredBy/><owner>bpeladmin</owner><conclusion/><state>ASSIGNED</state><subState>ASSIGNED</subState><processId>ResearchRequestWorkflow</processId><processName>ResearchRequestWorkflow</processName><versionNumber>1</versionNumber><notm>1</notm><taskGroupId/><taskType>http://blade-11.payveris.com:9700/orabpel/default/ResearchRequestWorkflow/1.0/taskConfigResearchRequest.xml</taskType><identificationKey>PAULA MERRILL, 2069</identificationKey><priority>3</priority><creator>bpeladmin</creator><creationDate>2006-02-23T14:53:08.000-05:00</creationDate><updatedBy>bpeladmin</updatedBy><modifyDate>2006-02-23T14:53:08.000-05:00</modifyDate><flexString1>1140724383057</flexString1><flexString2>PAULA MERRILL</flexString2><flexString3>PAULA MERRILL</flexString3><flexString4>PaymentId3489</flexString4><flexLong1>0</flexLong1><flexLong2>0</flexLong2><flexDouble1>0.0</flexDouble1><flexDouble2>0.0</flexDouble2><processVersion>1.0</processVersion><instanceId>2304</instanceId><domainId>default</domainId><approvers/><hasSubTasks>false</hasSubTasks><processOwner>bpeladmin</processOwner><pattern>SINGLE_APPROVAL</pattern><taskNumber>10240</taskNumber><systemString1/><systemString2/><systemString3/><versionReason>Task Created</versionReason><assigneeGroups>ResearchManager</assigneeGroups><payload confirmation_number="1140724383057" due_date="2006-02-22-05:00" reason="Payment not posted by payee"><requester xmlns="http://www.pp.com/schema"><first>PAULA MERRILL</first><last>PAULA MERRILL</last><tax_id/></requester><payment_type xmlns="http://www.pp.com/schema" number="">insuranceauto</payment_type><record_info xmlns="http://www.pp.com/schema"><creation app="EU" by="282950" date="2006-02-23T14:53:03.056-05:00"/><updation app="EU" by="282950" date="2006-02-23T14:53:03.056-05:00"/></record_info><payment xmlns="http://www.pp.com/schema" id="3489"><bank_info bank_id="2" funds_model="RISK"/><payment_info><confirmation_number>5428</confirmation_number><amount formattedValue="77.00" value="77"/><payment_date>2006-01-06-05:00</payment_date><check_number>5851</check_number><funded>false</funded><merged>false</merged><network id="3" status="ACTIVE" type="C">MOORE</network><alert_on_completion>false</alert_on_completion><alert_number_days_before>0</alert_number_days_before><scheduled_info id="2278"><scheduled_for_date formatted="01/06/2006">2006-01-06-05:00</scheduled_for_date><scheduled_on_date formatted="01/06/2006">2006-01-06-05:00</scheduled_on_date><created_user_id>282950</created_user_id><updated_user_id>0</updated_user_id></scheduled_info></payment_info><payee_info id="24958" relationship_id="6004"><payee_account_number>JUNIT123</payee_account_number><nick_name>blahblah</nick_name><name>complexpayeenameforatest</name><address1>123 main street</address1><address2>c/o anybody</address2><city>Dark Cityrandomizer</city><state>CT</state><zip>06512</zip><network id="3" status="ACTIVE" type="C">MOORE</network></payee_info><customer_info id="2069"><name>PAULA MERRILL</name><customer_account_id>8</customer_account_id><customer_account_number>213</customer_account_number><customer_routing_number>111111111</customer_routing_number><address1>Ernest Hemingway Drive</address1><city>Springfield</city><state>IL</state><zip>62703</zip></customer_info><state_info><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>958</network_batch_id><state_date>2006-10-24-05:00</state_date><state formatted="Check Cashed by Payee" id="2">Cleared</state><trace_number>211170100000003</trace_number></state_info><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>0</money_batch_id><good_funds_batch_id>0</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="6">Created</state><record_info><creation app="BPEL" by="0" date="2006-01-06T11:14:33-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>0</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="6">Created</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T11:14:35-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>0</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="22">Waiting for Decision</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T11:14:36-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="12">Ready for Funding</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:40:01-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="9">Funded</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:40:01-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>0</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="12">Ready for Funding</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:40:03-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>958</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="9">Funded</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:43:56-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>958</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="Mailed" id="11">Payment Sent</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:43:59-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>958</network_batch_id><state_date>2006-10-24-05:00</state_date><state formatted="Check Cashed by Payee" id="2">Cleared</state><trace_number>211170100000003</trace_number><record_info><creation app="EU" by="9999999" date="2006-02-03T12:38:08-05:00"/></record_info></state_history><record_info><creation app="BPEL" by="0" date="2006-01-06T11:14:33-05:00"/><updation app="EU" by="9999999" date="2006-02-03T12:38:08-05:00"/></record_info><research_request>false</research_request></payment></payload></task>
When Im look at the same task in the BPELConsole, the task looks like:
<task>
<title>Payment not posted by payee</title>
<assigneeUsers/>
<assigneeGroups>ResearchManager</assigneeGroups>
<acquiredBy/>
<owner>bpeladmin</owner>
<payload confirmation_number="1140724383057" due_date="2006-02-22-05:00" reason="Payment not posted by payee" >
<requester>
<first>PAULA MERRILL</first>
<last>PAULA MERRILL</last>
<tax_id/>
</requester>
<payment_type number="" >insuranceauto</payment_type>
<record_info>
<creation app="EU" by="282950" date="2006-02-23T14:53:03.056-05:00" />
<updation app="EU" by="282950" date="2006-02-23T14:53:03.056-05:00" />
</record_info>
<payment id="3489" >
<bank_info bank_id="2" funds_model="RISK" />
<payment_info>
<confirmation_number>5428</confirmation_number>
<amount formattedValue="77.00" value="77" />
<payment_date>2006-01-06-05:00</payment_date>
<check_number>5851</check_number>
<funded>false</funded>
<merged>false</merged>
<network id="3" status="ACTIVE" type="C" >MOORE</network>
<alert_on_completion>false</alert_on_completion>
<alert_number_days_before>0</alert_number_days_before>
<scheduled_info id="2278" >
<scheduled_for_date formatted="01/06/2006" >2006-01-06-05:00</scheduled_for_date>
<scheduled_on_date formatted="01/06/2006" >2006-01-06-05:00</scheduled_on_date>
<created_user_id>282950</created_user_id>
<updated_user_id>0</updated_user_id>
</scheduled_info>
</payment_info>
<payee_info id="24958" relationship_id="6004" >
<payee_account_number>JUNIT123</payee_account_number>
<nick_name>blahblah</nick_name>
<name>complexpayeenameforatest</name>
<address1>123 main street</address1>
<address2>c/o anybody</address2>
<city>Dark Cityrandomizer</city>
<state>CT</state>
<zip>06512</zip>
<network id="3" status="ACTIVE" type="C" >MOORE</network>
</payee_info>
<customer_info id="2069" >
<name>PAULA MERRILL</name>
<customer_account_id>8</customer_account_id>
<customer_account_number>213</customer_account_number>
<customer_routing_number>111111111</customer_routing_number>
<address1>Ernest Hemingway Drive</address1>
<city>Springfield</city>
<state>IL</state>
<zip>62703</zip>
</customer_info>
<state_info>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>958</network_batch_id>
<state_date>2006-10-24-05:00</state_date>
<state formatted="Check Cashed by Payee" id="2" >Cleared</state>
<trace_number>211170100000003</trace_number>
</state_info>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>0</money_batch_id>
<good_funds_batch_id>0</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="6" >Created</state>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T11:14:33-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>0</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="6" >Created</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T11:14:35-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>0</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="22" >Waiting for Decision</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T11:14:36-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="12" >Ready for Funding</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:40:01-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="9" >Funded</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:40:01-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>0</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="12" >Ready for Funding</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:40:03-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>958</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="9" >Funded</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:43:56-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>958</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="Mailed" id="11" >Payment Sent</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:43:59-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>958</network_batch_id>
<state_date>2006-10-24-05:00</state_date>
<state formatted="Check Cashed by Payee" id="2" >Cleared</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="EU" by="9999999" date="2006-02-03T12:38:08-05:00" />
</record_info>
</state_history>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T11:14:33-05:00" />
<updation app="EU" by="9999999" date="2006-02-03T12:38:08-05:00" />
</record_info>
<research_request>false</research_request>
</payment>
</payload>
<conclusion/>
<state>ASSIGNED</state>
<subState>ASSIGNED</subState>
<processId>ResearchRequestWorkflow</processId>
<processName>ResearchRequestWorkflow</processName>
<processVersion>1.0</processVersion>
<instanceId>2304</instanceId>
<domainId>default</domainId>
<processOwner>bpeladmin</processOwner>
<taskId>0D7B97F1B138EE21E04017AC2B194357</taskId>
<versionReason>Task Created</versionReason>
<taskGroupId/>
<taskType>http://blade-11.payveris.com:9700/orabpel/default/ResearchRequestWorkflow/1.0/taskConfigResearchRequest.xml</taskType>
<identificationKey>PAULA MERRILL, 2069</identificationKey>
<comments/>
<priority>3</priority>
<creator>bpeladmin</creator>
<updatedBy>bpeladmin</updatedBy>
<hasSubTasks>false</hasSubTasks>
<approvers/>
<pattern>SINGLE_APPROVAL</pattern>
<flexString1>1140724383057</flexString1>
<flexString2>PAULA MERRILL</flexString2>
<flexString3>PAULA MERRILL</flexString3>
<flexString4>PaymentId3489</flexString4>
<flexDouble1/>
<flexDouble2/>
<flexLong1/>
<flexLong2/>
<flexDate1/>
<flexDate2/>
<flexDate3/>
<attachment/>
<taskNumber>10240</taskNumber>
<creationDate>2006-02-23T14:53:08.955-05:00</creationDate>
<modifyDate>2006-02-23T14:53:08.955-05:00</modifyDate>
<isGroup>true</isGroup>
<versionNumber>1</versionNumber>
<notm>1</notm>
<expirationDate/>
<expirationDuration/>
</task>
Message was edited by:
gjacobi

I am using oracle.tip.pc.services.hw.task.impl.Task
that object has a toXML method.
To get that object, I am using the RemoteWorklistServiceClient.getWorlistTaskById method.
A word of caution. Not only am I still having the issue above (I had to hack my own WorkflowTask.xsd to make it validate) but I have noticed that the toXML() method actually returns different results when you think it would not. For example, I have something similar to the following code:
task.toXML()
task.toElement()
task.getPayload()
task.toXML()
The first and last toXML methods produce strings that do not match (it adds some empty elements to the end of the document). Weird. Very Weird.
Greg

ERROR: "info.plist does not validate against DTD"

Hi! I got this error if anyone has it solved Please HELP.
I am trying to package a WRT widget using Nokia WRT extension for Adobe Dreamweaver. This is the place for info on the extension: http://www.forum.nokia.com/Tools_Docs_and_Code/Tools/Runtimes/Web_Runtime/
I figure developer from here who use DW to develop mobile content might know the error.
When come to the step of 'Package Nokia WRT Widget' I got this error: info.plist does not validate against DTD
and a page of error info shown like this:
DTD validated at: Wed Jun 17 2009 19:03:00 GMT+0800 (Malay Peninsula Standard Time)
DTD used for validation: http://www.nokia.com/DTDs/plist-1.0.dtd
Line
Column
Message
Explanation
Source
2
95
DTD did not contain element declaration for document type name
3
16
Attribute "version" exists, but can not be used for this element.
3
21
element "plist" undefined. Did you mean "applet" or "strike"?
4
7
element "dict" undefined. Did you mean "strike" or "input"?
5
7
element "key" undefined. Did you mean "strike" or "blockquote"?
6
10
element "string" undefined. Did you mean "strong" or "strike"?
7
7
element "key" undefined. Did you mean "strike" or "blockquote"?
8
10
element "string" undefined. Did you mean "strong" or "strike"?
9
7
element "key" undefined. Did you mean "strike" or "blockquote"?
10
10
element "string" undefined. Did you mean "strong" or "strike"?
11
7
element "key" undefined. Did you mean "strike" or "blockquote"?
12
10
element "string" undefined. Did you mean "strong" or "strike"?
13
7
element "key" undefined. Did you mean "strike" or "blockquote"?
14
9
element "true" undefined. Did you mean "textarea" or "tr"?
Can anyone knows what this means and how i can solve it?
Please help. Thankyou.
note: I am new here and knows that keep asking quesion without giving back is not good but I have a deadline here and wanted to finish the job. I will read some other post and try to help in return when I am able to do so.

Hi pziecina,
Thanks for your reply,
I suspect my problem is the installation or setup of my system or software. as the result i tested is not by doing any scripting at all. All I did is following one of their example exactly (http://www.forum.nokia.com/Tools_Docs_and_Code/Tools/Runtimes/Web_Runtime/Dreamweaver_Exte nsion/QuickStart.xhtml) and package strightaway without modifying the code. because I want to make sure i got the extension install correctly. even so by packaging one of their ready make example already yield this error.

Getting Error in java mapping: Parsing empty source. Root element expected!

Hi Experts,
   I am using java mapping for schema validation of input message. I have followed all the standard procedures and implemented the java class in the interface mapping.
My interface mapping is like this:
OrderData --->Java Class ---SchemaValidate
                     Mesg Map ---OrderData_to_BAP --->BAPI Msg
So first I want to validate the schema of the input message. If the input message is invalid then XI should throw an exception. Then I use the actual message mapping to map the input order data to the BAPI input parameters.
In the java code I am using xerces parser.
The java code works fine when I run it as a standalone application.
The interface mapping also works fine if I don't include the java mapping. Ofcourse schema validation does not happen.
But when I test the interface mapping by including the java mapping then I am getting the error:
Call method execute of the application Java mapping SchemaValidate
Java mapping SchemaValidate completed. (execute() of SchemaValidate
com.sap.aii.utilxi.misc.api.BaseRuntimeException: Parsing an empty source. Root element expected!
What am I doing wrong? Why it is not getting the root element?
My Java code is as follows:
import com.sap.aii.mapping.api.StreamTransformation;
import com.sap.aii.mapping.api.StreamTransformationConstants;
import com.sap.aii.mapping.api.StreamTransformationException;
import java.io.*;
import java.util.Map;
import javax.xml.parsers.*;
import org.xml.sax.helpers.*;
import org.xml.sax.*;
import org.apache.xerces.jaxp.*;
Sample mapper for SAP-XI
@author Gopal
public class SchemaValidate implements StreamTransformation {
    //Constants when using XML Schema for SAX parsing.
     static final String JAXP_SCHEMA_LANGUAGE =
     "http://java.sun.com/xml/jaxp/properties/schemaLanguage";
     static final String W3C_XML_SCHEMA =
     "http://www.w3.org/2001/XMLSchema";
     static final String JAXP_SCHEMA_SOURCE =
     "http://java.sun.com/xml/jaxp/properties/schemaSource";
Injection of mapping parameters
from integration engine
@param map Map with configuration data
    public void setParameter(Map map) {
Mapping implementation
@param inputStream Input data from integration engine
@param outputStream Output data to integration engine
    public void execute(InputStream inputStream,
                        OutputStream outputStream)
      throws StreamTransformationException {
        try {
              // obtain an object of class javax.xml.parsers.SAXParser,
              SAXParserFactory spf = SAXParserFactoryImpl.newInstance();
              spf.setNamespaceAware(true);
              spf.setValidating(true);
              SAXParser sp = spf.newSAXParser();
              // setup the schema file
              sp.setProperty(JAXP_SCHEMA_LANGUAGE, W3C_XML_SCHEMA);
              sp.setProperty(JAXP_SCHEMA_SOURCE, new File("IOReqMsgSchema.xsd"));
              //parse the input xml using the given schema
              sp.parse(inputStream, new ParseErrorHandler());
        catch(SAXException se) {
          se.printStackTrace();
        catch ( Exception e ) {
          throw new StreamTransformationException( e.getMessage() );
My input message is :
<?xml version="1.0" encoding="UTF-8"?>
<ns0:OrderCreate_request xmlns:ns0="mynamespace">
   <ORDER>HTEST1234567</ORDER>
   <ORDER_TYPE>z001</ORDER_TYPE>
   <ORDER_NAME>Test Order</ORDER_NAME>
   <CO_AREA>INTC</CO_AREA>
   <CCTR_POSTED>1234567890888888888</CCTR_POSTED>
   <CURRENCY>USD</CURRENCY>
   <PERSON_RESP>12345679</PERSON_RESP>
</ns0:OrderCreate_request>
Kindly help! please this is urgent!!!!!!
Thanks
Gopal
Edited by: gopalkrishna baliga on Feb 28, 2008 9:34 AM

Hi Stefan,
   I did the code changes to return output stream and the java code works perfectly in standalone mode in my PC.
   But when I use the same in the Java mapping with XI then It throws an error "Getting Error in java mapping: Parsing empty source. Root element expected!".
My XI J2EE server has JDK1.4.3.11.
Is there any limitation of using SAX parser in XI? If Yes, then which parser should be used for schema validation in XI?
I have included the XSD file for schema validation along with class files in the .jar file. This jar file is then imported in XI repository. Is the XI engine not able to read the XSD file?
Do I have to handle reading XSD file differently? Any suggession how?
Is this parser error due to some security access?
Kindly help me! I have been struggling with this problem since 2 weeks. I will be greatfull to you if you can help me.
Thanks
Gopal

Namespace prefix in Root element missing during variable assignment

In bpel 10.1.3.4, I need qualified element Namespaces in one of the target variables. I have an xsd that has elementFormDefault = "qualified" set, therefore all elements being referred to would have the namespace prefixed. This is working for all child elements, but not the root element. How can i get the root element prefixed with the namespace?
If i use transform or copy/append operation to populate in the target variable the variable gets populated something like this :
<Invoice xmlns:pidx="http://www.api.org/pidXML/v1.0" pidx:transactionPurposeIndicator="Original" pidx:version="1.0" xmlns="http://www.api.org/pidXML/v1.0">
<pidx:InvoiceProperties>
<pidx:InvoiceNumber>test123</pidx:InvoiceNumber>
</pidx:InvoiceProperties>
</Invoice>
Whereas i need :
<*pidx:*Invoice xmlns:pidx="http://www.api.org/pidXML/v1.0" pidx:transactionPurposeIndicator="Original" pidx:version="1.0" xmlns="http://www.api.org/pidXML/v1.0">
<pidx:InvoiceProperties>
<pidx:InvoiceNumber>test123</pidx:InvoiceNumber>
</pidx:InvoiceProperties>
</*pidx:*Invoice>
Is there some way to accomplish this?
Regards,
Sandeep

Hi Sandeep,
We have exactly the same issue, but, when we implemented the solution, we are getting the following error, when we tried to compile the code, we are using 11.1.1.4.0 version of SOA 11g, appreciate if there is any way you can help us on this:
Jul 12, 2011 2:40:28 PM com.collaxa.cube.CubeLogger info
INFO: validating "BPELProcess1.bpel" ...
oracle.jrf.UnknownPlatformException: JRF is unable to determine the current application server platform.
     at oracle.jrf.ServerPlatformSupportFactory.getInstance(ServerPlatformSupportFactory.java:79)
     at oracle.integration.platform.blocks.WLSPlatformConfigurationProvider.<clinit>(WLSPlatformConfigurationProvider.java:44)
     at oracle.integration.platform.blocks.FabricConfigManager.<clinit>(FabricConfigManager.java:154)
     at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXpathFunctions(FabricXPathFunctionResolver.java:282)
     at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXPathConfigFile(FabricXPathFunctionResolver.java:156)
     at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.init(FabricXPathFunctionResolver.java:49)
     at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.loadFabricXpathFunctions(BPELXPathFunctionNameResolver.java:57)
     at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<init>(BPELXPathFunctionNameResolver.java:48)
     at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<clinit>(BPELXPathFunctionNameResolver.java:44)
     at com.collaxa.cube.lang.compiler.bpel.XPathExprValidatorVisitor.<init>(XPathExprValidatorVisitor.java:122)
     at com.collaxa.cube.lang.compiler.bpel.AssignValidator.<init>(AssignValidator.java:89)
     at com.collaxa.cube.lang.compiler.bpel.BpelParser.<init>(BpelParser.java:452)
     at com.collaxa.cube.lang.compiler.bpel.BPELValidator.validate(BPELValidator.java:60)
     at com.collaxa.cube.lang.compiler.BPEL1Processor.validate(BPEL1Processor.java:329)
     at com.collaxa.cube.lang.compiler.BPEL1Processor.process(BPEL1Processor.java:153)
     at com.collaxa.cube.lang.compiler.CubeParserHelper.compile(CubeParserHelper.java:47)
     at oracle.fabric.bpel.bpelc.BPELComponentValidator.validate(BPELComponentValidator.java:40)
     at oracle.soa.scac.ValidateComposite.validateComponentTypeServicesReferences(ValidateComposite.java:1117)
     at oracle.soa.scac.ValidateComposite.doValidation(ValidateComposite.java:500)
     at oracle.soa.scac.ValidateComposite.run(ValidateComposite.java:150)
     at oracle.soa.scac.ValidateComposite.main(ValidateComposite.java:135)
Jul 12, 2011 2:40:29 PM CubeProcessGenerator compile
WARNING: classpath is: C:\oracle\Middleware\jdeveloper\jdev\extensions\oracle.sca.modeler.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\oracle\Middleware\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.mediator_11.1.1\mediator_client.jar;C:\oracle\Middleware\oracle_common\modules\oracle.mds_11.1.1\mdsrt.jar;C:\oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;C:\oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xml.jar;C:\oracle\Middleware\jdeveloper\jdev\extensions;;C:\JDeveloper\mywork\InvoiceTransferApp\InvoiceTransferProj\SCA-INF\classes;C:\JDeveloper\mywork\InvoiceTransferApp\InvoiceTransferProj\SCA-INF\classes;C:\JDeveloper\mywork\InvoiceTransferApp\InvoiceTransferProj\SCA-INF\gen-classes;C:\oracle\Middleware\oracle_common\modules\commonj.sdo_2.1.0.jar;C:\oracle\Middleware\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;C:\oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpel1-1-xbeans.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-common.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpel_coherence_config.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-exts.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\thirdparty.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpm-analytics.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-thirdparty.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\wsif-binding.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-validator.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\monitor-rt-xbean.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\oracle.soa.bpmn.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel1.jar;C:\oracle\Middleware\jdeveloper\soa\modules\user-patch.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.thirdparty.jar;C:\oracle\Middleware\jdeveloper\uddi\lib\oracle.soa.uddi.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\bpm-infra.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\testfwk-xbeans.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-ext.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-infra-scheduler.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\xmlunit-1.1.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-infra-tools.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-xpath-exts.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\oracle-soa-client-api.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.wls.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-client.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime-ext-was.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime-ext-wls.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\oracle.soa.fabric.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.ext_11.1.1\classes
Regards,
Sireesh

Xmldoc.createSchemaBasedXML validation only validates against root element?

Similar Messages

Maybe you are looking for