PARSER UNEXPECTED_VALUE

Hi All,
My scenario is SOAP to ABAP proxy, when I am testing the data thorugh SOAP UI tool, I am getting the error message as
<?xml version="1.0" encoding="UTF-8"?>
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header />
<SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Client</faultcode>
 <faultstring>Error during conversion of XI message</faultstring>
 <faultactor>http://sap.com/xi/XI/Message/30</faultactor>
 <detail>
 <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
 <SAP:Category>XIProtocol</SAP:Category>
 <SAP:Code area="PARSER">UNEXPECTED_VALUE</SAP:Code>
 <SAP:P1>Main/@versionMajor</SAP:P1>
 <SAP:P2>000</SAP:P2>
 <SAP:P3>003</SAP:P3>
 <SAP:P4 />
 <SAP:AdditionalText />
 <SAP:Stack>XML tag Main/@versionMajor has incorrect value 000; expected value is 003</SAP:Stack>
 </SAP:Error>
 </detail>
 </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
please provide your valuable suggestion

Boppana,
Try to hardcode the value 003 for the attribute versionMajor which is under Main segment in mapping. If it works then either you may send this value from source or hardcode it.
Regards,
---Satish

Similar Messages

Parser - "Unexpected value" error

Hi all,
I have a file to ABAP proxy scenario. The file is an XML file. In SXMB_MONI, I am getting the following error at "Call Adapter" step -
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="PARSER">UNEXPECTED_VALUE</SAP:Code>
<SAP:P1>Main/@versionMajor</SAP:P1>
<SAP:P2>002</SAP:P2>
<SAP:P3>003</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XML tag Main/@versionMajor has incorrect value 002; expected value is 003</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I verified that the source XML file has the value 003 for versionMajor attribute. So Header section of the message also shows the value 003.
Does anyone know what might be the reason for this ?
Regards,
Shankar

Hi,
Main/@versionMajor is XI message protocol version. Example: For the XI 3.0 message protocol VERSION_MAJOR = 3 and VERSION_MINOR = 0.
So try to pass these message header fields during a mapping.
http://help.sap.com/saphelp_nw04/helpdata/en/6e/ff0bf75772457b863ef5d99bc92404/frameset.htm
When you think, the message tries to call an inbound proxy in XI, you should check SXMB_ADM if the system is maintained as XI and not as application system.
Thanks
Swarup
Edited by: Swarup Sawant on May 26, 2008 10:36 AM

Error during saving a multipart message

Hi All,
We are currently integrating third party system with SAP ECC as a part of our FICA implementation.
We have configured soap adapter initially at the sender side and IDoc adapter at the reciever intially. After looking at the performnace of the soap adapter, we thought of using HTTP sender instead of a soap sender, so that the webservice makes a direct call to PI integration engine instead of Adapter engine.
Now my scenario looks like.
Java/J2EE client -> webservice call > XI pipeline>SAP.
So here , i havent used http adapter at the source side.
My problem is when i call the XI pipleine url as suggested by the below blog
<a href="/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine Soap Inbound channel of the Integration engine</a>
I am getting the follwoing error as seen below
May 31, 2007 6:05:50 PM com.sun.xml.messaging.saaj.soap.MessageImpl saveChanges

SEVERE: SAAJ0540: Error during saving a multipart message
But for my scenario, i havent used any soap with attachments to pass through PI.
My soap message is a simple soap envelope with soap part-message.(body).
Please do help me out in resolving this issue.
Thanks & Regards,
Dhana
null

Hi Steve,
My Soap Action is already applied and I traced out few options after googling it up and added few jars (xalan.jar and saxon8.jar). Even now I am getting the same error.
Please do tell me what to do in this regard.
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
</SOAP:Header>
<SOAP:Body>
<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during conversion of XI message</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="PARSER">UNEXPECTED_VALUE</SAP:Code><SAP:P1>Main/@versionMajor</SAP:P1><SAP:P2>000</SAP:P2><SAP:P3>003</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>XML tag Main/@versionMajor has incorrect value 000; expected value is 003
</SAP:Stack></SAP:Error></detail></SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Soap Error message:Error during conversion of XI message
Thanks,
Dhana

Http-Status: 500 Error during conversion of XI message

i am getting this error, Could you please help us in resolving this
http-Status: 500 Error during conversion of XI message
Payload:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
</SOAP:Header>
<SOAP:Body>
<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during conversion of XI message</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="PARSER">UNEXPECTED_VALUE</SAP:Code><SAP:P1>Main/@versionMajor</SAP:P1><SAP:P2>000</SAP:P2><SAP:P3>003</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>XML tag Main/@versionMajor has incorrect value 000; expected value is 003
</SAP:Stack></SAP:Error></detail></SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Thnaks, ajay

XML tag Main/@versionMajor has incorrect value 000; expected value is 003
as mentioned above @versionMajor is expecting 003 as the input....if it a DataType in XI then check if there is some restriction imposed on the above attribute.....if you are importing some XSD/wsdl then check if it has some restriction.......if the restriction is not needed then try removing it....so that versionMajor will accept all the values
Regards,
Abhishek.

Problem sending the data into XI through webservice

Dear All,
I am getting an error while sending the data into XI after hitting my webservice.
SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
</SOAP:Header>
<SOAP:Body>
<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>SOAP:Client</faultcode>
<faultstring>Error during conversion of XI message</faultstring>
<faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail>
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="PARSER">UNEXPECTED_VALUE</SAP:Code>
<SAP:P1>Main/@versionMajor</SAP:P1>
<SAP:P2>000</SAP:P2>
<SAP:P3>003</SAP:P3>
<SAP:P4/>
<SAP:AdditionalText/>
<SAP:ApplicationFaultMessage namespace=""/>
<SAP:Stack>XML tag Main/@versionMajor has incorrect value 000; expected value is 003
</SAP:Stack></SAP:Error></detail></SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Please suggest what the problem could be.
Abhishek

<SAP:Stack>XML tag Main/@versionMajor has incorrect value 000; expected value is 003
</SAP:Stack></SAP:Error></detail></SOAP:Fault>
--> this states as it is version problem
Main/@versionMajor is XI message protocol version
check SXMB_ADM if the system is maintained as XI

Error implementing Web Service of PI7.0

Hi all:
We released a Web Service in PI. But when we implement it from Web Dynpro, it throws the "SOAPFaultException" exception.Detail message is:
<detail xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1"> <SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="PARSER">UNEXPECTED_VALUE</SAP:Code>
<SAP:P1>Main/@versionMajor</SAP:P1>
<SAP:P2>000</SAP:P2>
<SAP:P3>003</SAP:P3>
<SAP:P4/>
<SAP:AdditionalText/>
<SAP:ApplicationFaultMessage namespace=""/>
<SAP:Stack>XML tag Main/@versionMajor has incorrect value 000; expected value is 003</SAP:Stack> </SAP:Error>
</detail>
Has anybody met this problem before?

Hi Lou
This will help u..
http://help.sap.com/saphelp_nw70/helpdata/en/be/1f9a3dcbcfac53e10000000a114084/frameset.htm
regards,
vasanth

Urgent : Soap Receiver Adapter

Hi
Im using SOAP adapter on receiver side to call a web service. Initialy when i tried my end to end scenario I got the following error -
2007-08-07 05:30:57 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault.
So in order to find out the exact error I used HTTP client and now im getting the error as -
Result:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
</SOAP:Header>
<SOAP:Body>
<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during conversion of XI message</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="PARSER">UNEXPECTED_VALUE</SAP:Code><SAP:P1>Main/@versionMajor</SAP:P1><SAP:P2>000</SAP:P2><SAP:P3>003</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>XML tag Main/@versionMajor has incorrect value 000; expected value is 003
</SAP:Stack></SAP:Error></detail></SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Can anyone explain what does this error mean?
Vaibhav

no i just used HTTP client to fire the webservice... it gives a more exact worded error
anyways i worked on it some error and pinpointed the exact error 'Base exception in EJB'... some problem with the EJB that i used as a webservice but when i check the WS in the navigator, it works fine.
Can anyone tell me what cud be the problem with XI not able to communicate with EJB exposed as web service??
Vaibhav

Error "XML tag Main/@versionMinor has incorrect value 001; expected value."

I'm going to describe our scenario.
We have created an Abap proxy in a BW system to run a XI interface. The abap proxy in BW is connected to the IE of a XI 3.0 system. That scenario runs without problems with BW 3.5 (basis 6.40). Now, we are migrating the release of BW to 7.30. we have created the Abap proxy in the migrated BW system but when we run the interface the next message is returned:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="PARSER">UNEXPECTED_VALUE</SAP:Code>
<SAP:P1>Main/@versionMinor</SAP:P1>
<SAP:P2>001</SAP:P2>
<SAP:P3>000</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>XML tag Main/@versionMinor has the incorrect value 001. Value 000 expected</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
does anyone know what the problem is? is there a version conflict between BW 7.3 and XI 3.0?
Thanks very much

Hi,
I'm not an expert, but it might be that you would also need to update the XI content to match the new release and then regenerate the proxy.
It does indeed seem to be a difference in the version of the proxies between BW 3.5 and BW 7.3.
Regards,
Horia

XML tag Main/@versionMajor has incorrect value 002; expected value is 003

Dear experts!
I have created a file to proxy scenario. When sent out of XI the following message occurs:
O, btw, I have tried both XI 2.0 and 3.0 in the comm. channel and a fault message is present.
What's the matter???
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="PARSER">UNEXPECTED_VALUE</SAP:Code>
<SAP:P1>Main/@versionMajor</SAP:P1>
<SAP:P2>002</SAP:P2>
<SAP:P3>003</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XML tag Main/@versionMajor has incorrect value 002; expected value is 003</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks for your suggestions!
Will reward points if answers are helpful

Hi.
Can you copy past your xml input payload...
Check out this thread...he has same issue...n its resolved..
XI 3.0 and external Java client/web service
Use the url:
http://hostname:port/XISOAPAdapter/MessageServlet?version=3.0&channel=:SOAPRequest:SOAPIn
Nilesh
Message was edited by:
Nilesh Kshirsagar

How can I use a 3rd party XML parser such as xerces with OC4J ?

Hi all tech experts,
I am using Oracle Application Server 10g Release 2 (10.1.2) and i have
installed Portal and Wireless and OracleAS Infrastructure on the same
computer.
i tried all the solutions on this thread
Use of Xerces Parser in out application with Oracle App Server 9.0.4
but still fighting.
I have also posted this query on OTN on following thread
How can I use a 3rd party XML parser such as xerces with OC4J?
but no reply....
Please help me on this issue.
Since OC4J is preconfigured to use the Oracle XML parser which is xmlparserv2.jar.
i have read the following article which states that
OC4J is preconfigured to use the Oracle XML parser. The Oracle XML parser is fully JAXP 1.1 compatible and will serve the needs of applications which require JAXP functionality. This approach does not require the download, installation, and configuration of additional XML parsers.
The Oracle XML parser (xmlparserv2.jar) is configured to load as a system level library of OC4J through it's inclusion as an entry in the Class-Path entry of the oc4j.jar Manifest.mf file. This results in the Oracle XML parser being used for all common deployment and packaging situations. You are not permitted to modify the Manifest.mf file of oc4j.jar.
It must be noted that configuring OC4J to run with any additional XML parser or JDBC library is not a supported configuration. We do know customers who have managed to successfully replace the system level XML parser and the Oracle JDBC drivers that ship with the product, but we do not support this type of configuration due to the possibility of unexpected system behavior and system errors that might occur from replacing the tested and certified libraries.
If you absolutely must use an additional XML parser such as xerces, then you have to start OC4J such that the xerces.jar file is loaded at a level above the OC4J system classpath. This can be accomplished using the -Xbootclasspath flag of the JRE.
i have also run the following command
java -Xbootclasspath/a:d:\xerces\xerces.jar -jar oc4j.jar
but no success.
How could i utilize my jar's like xerces.jar and xalan.jar for parsing instead of OC4J in-built parser ?
All reply will be highly appreciated.
Thnx in advance to all.
Neeraj Sidhaye
try_catch_finally @ Y !

Hi Neeraj Sidhaye,
I am trying to deploy a sample xform application to the Oracle Application Server (10.1.3). However, I encountered the class loader issue that is similar to your stuation. I tried all the three solutions but the application is still use the Oracle xml paser class. I am wondering if you have any insight about this?
Thanks for your help.
Xingsheng Qian
iPass Inc.
Here is the error message I got.
Message:
java.lang.ClassCastException: oracle.xml.parser.v2.XMLElement
Stack Trace:
org.chiba.xml.xforms.exception.XFormsException: java.lang.ClassCastException: oracle.xml.parser.v2.XMLElement
     at org.chiba.xml.xforms.Container.dispatch(Unknown Source)
     at org.chiba.xml.xforms.Container.dispatch(Unknown Source)
     at org.chiba.xml.xforms.Container.initModels(Unknown Source)
     at org.chiba.xml.xforms.Container.init(Unknown Source)
     at org.chiba.xml.xforms.ChibaBean.init(Unknown Source)
     at org.chiba.adapter.servlet.ServletAdapter.init(ServletAdapter.java:153)
     at org.chiba.adapter.servlet.ChibaServlet.doGet(ChibaServlet.java:303)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:719)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:299)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:187)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassCastException: oracle.xml.parser.v2.XMLElement
     at org.chiba.xml.xforms.Instance.iterateModelItems(Unknown Source)
     at org.chiba.xml.xforms.Bind.initializeModelItems(Unknown Source)
     at org.chiba.xml.xforms.Bind.init(Unknown Source)
     at org.chiba.xml.xforms.Initializer.initializeBindElements(Unknown Source)
     at org.chiba.xml.xforms.Model.modelConstruct(Unknown Source)
     at org.chiba.xml.xforms.Model.performDefault(Unknown Source)
     at org.chiba.xml.xforms.XFormsDocument.performDefault(Unknown Source)
     at org.chiba.xml.xforms.XFormsDocument.dispatchEvent(Unknown Source)
     at org.apache.xerces.dom.NodeImpl.dispatchEvent(Unknown Source)
     ... 18 more

Xml parsing error in JSP 1.2

Hi, everyone.
I'm getting an error trying precompile JSP code using a variable tag in my tag library to define a new scripting variable : Element "tag" does not allow "variable" here.
I also get the same error after deployng the JSP code on Sun One Application server 7.
Any idea?
Thanks a lot for any help.

Here is the tag lib file that can't be parsed.
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE taglib
PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.2//EN"
 "http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_2.dtd">

<taglib>
<tlib-version>1.0</tlib-version>
<jsp-version>1.2</jsp-version>
<short-name>er</short-name>
<uri></uri>
<description>
 A tab library for iteration tag used in Event Reminder application
</description>
<tag>
<name>loopEvent</name>
<tag-class>com.abnamro.na.net.reminder.servlet.IterateTag</tag-class>
<body-content>JSP</body-content>
<attribute>
<name>collection</name>
<required>true</required>
<rtexprvalue>true</rtexprvalue>
</attribute>
<variable>
 <name-given>mmdd</name-given>
 <variable-class>String</variable-class>
 <declare>true</declare>
 <scope>NESTED</scope>
 <description>month and day of event</description>
</variable>
<variable>
 <name-given>type</name-given>
 <variable-class>String</variable-class>
 <declare>true</declare>
 <scope>NESTED</scope>
 <description>This variable contains type of event</description>
</variable>
<variable>
 <name-given>name</name-given>
 <variable-class>String</variable-class>
 <declare>true</declare>
 <scope>NESTED</scope>
 <description>This variable contains name of event</description>
</variable>
<variable>
 <name-given>period</name-given>
 <variable-class>String</variable-class>
 <declare>true</declare>
 <scope>NESTED</scope>
 <description>period over which a user get a email for</description>
</variable>
<variable>
 <name-given>descr</name-given>
 <variable-class>String</variable-class>
 <declare>true</declare>
 <scope>NESTED</scope>
 <description>description</description>
</variable>
<variable>
 <name-given>numyears</name-given>
 <variable-class>String</variable-class>
 <declare>true</declare>
 <scope>NESTED</scope>
 <description>number of years for particular event</description>
</variable>
<variable>
 <name-given>address</name-given>
 <variable-class>String</variable-class>
 <declare>true</declare>
 <scope>NESTED</scope>
 <description>address of event</description>
</variable>
<variable>
 <name-given>phone</name-given>
 <variable-class>String</variable-class>
 <declare>true</declare>
 <scope>NESTED</scope>
 <description>phone of event</description>
</variable>
</tag>
</taglib>
Thank you.

Issue in parsing the response of a WebService in Service Link

I am getting issues in connecting an external (non cisco) application via WebService. Appreciate if anyone can help in fixing the issue. I am using 9.3.2 Patch 6.
Connectivity to an external system (a 3rd party application in my firm) was achieved via WebService using the ServiceLink module.
Used the Outbound HTTP/WS Adapter where I am sending request and receiving response (bi-direction).
Successfully constructed and passed the XML request to the WebService.
Received response from the WebService as an XML / Soap Message which is then wrapped with the <Message> tag with the channel-id attribute successfully.
Designed a XSL Transformation (For this WebService, the XSLT did not generated automatically) which, I hope is not being applied properly in CPSC; but working fine outside of CPSC when I have checked the response XML with the XSLT in an online editor (http://www.freeformatter.com/xsl-transformer.html). Everything looks perfect in this editor where I have issues in CPSC.
I am getting a Transformation exception in CPSC and the response message was unable to convert into the nsXML. The exception I am receiving is below. Not sure whether it is due to the namespace or something else..
Note: I am having this issue in this Agent/WebService alone. I have tested with couple other WebServices where I didn't have any issues in getting the response and update the field in CPSC form successfully. So, I believe that there are no issues in the parser in our server.
Exception Received:
org.xml.sax.SAXParseException: Premature end of file. at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124) at com.newscale.bfw.util.XMLValidator.validate(XMLValidator.java:147) at com.newscale.is.core.MessageExecutor.processNSTaskTransportMessage(MessageExecutor.java:135) at com.newscale.is.core.MessageExecutor.processTransportMessage(MessageExecutor.java:431) at com.newscale.is.core.MessageExecutor.processSynchronousOutboundMessage(MessageExecutor.java:526) at com.newscale.is.adk.OutboundAdapterUtil.processSynchronousResponse(OutboundAdapterUtil.java:44) at com.newscale.is.adapter.http.HTTPOutboundAdapter.call(HTTPOutboundAdapter.java:190) at com.newscale.is.adapter.http.HTTPOutboundAdapter.processMessage(HTTPOutboundAdapter.java:147) at com.newscale.is.core.MessageRouter.routeMessage(MessageRouter.java:115) at com.newscale.is.core.MessageExecutor.processOutboundMessage(MessageExecutor.java:604) at com.newscale.is.core.MessageExecutor.processMessage(MessageExecutor.java:125) at com.newscale.is.core.QueueListener.handleTextMessage(QueueListener.java:91) at sun.reflect.GeneratedMethodAccessor110.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.camel.component.bean.MethodInfo.invoke(MethodInfo.java:340) at org.apache.camel.component.bean.MethodInfo$1.proceed(MethodInfo.java:237) at org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:168) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:99) at org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:73) at org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:101) at org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:71) at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.SendProcessor$2.doInAsyncProducer(SendProcessor.java:115) at org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:285) at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:110) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:71) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:322) at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:213) at org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:303) at org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.UnitOfWorkProcessor.processAsync(UnitOfWorkProcessor.java:150) at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:117) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:71) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:86) at org.apache.camel.component.jms.EndpointMessageListener.onMessage(EndpointMessageListener.java:105) at org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:561) at org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:499) at org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467) at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325) at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263) at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1059) at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1051) at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:948) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)
Sample XML File received as response from the WebService – which then wrapped with the <message> tag along with appropriate channel-id.
<message channel-id="10a60e45-65d4-40c0-826f-1a91d2135da0">
<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<ns:ITSPResponse xmlns:ns="urn:PegaRULES:SOAP:BNYMDataITSPTest:Services">
<Output>Test IT Service Portal - 1</Output>
</ns:ITSPResponse>
</soap:Body>
</soap:Envelope>
</message>
XSL Transformation
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="
http://www.w3.org/1999/XSL/Transform" xmlns:ns="urn:PegaRULES:SOAP:BNYMDataITSPTest:Services">
<xsl:template match="/">
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns="urn:PegaRULES:SOAP:BNYMDataITSPTest:Services">
<message>
<xsl:attribute name="channel-id">
<xsl:value-of select="//@*[local-name()='channel-id']" />
</xsl:attribute>
<send-parameters>
<agent-parameter>
<name>Output</name>
<value> <xsl:value-of select="//*[local-name()='Output']" /> </value>
</agent-parameter>
</send-parameters>
</message>
</xsl:template>
</xsl:stylesheet>

The reply I got from Cisco Engineering team for this is to get the response as a soap message than XML data.
The tag should not be available in the response received. If we don't have this, the response will still consider as a valid XML / Soap message after wrapped by the tag.
If we have the tag in the response, after wrapping the tag, the format of the response will not be in good format.
Also, Cisco Engineering team has confirmed that it is not possible to remove the tag from CPSC. It should be removed by the WebService providers while sending the response.
For my case, I am consuming the WebService from a tool similar to CPSC where the entire settings has to be changed to send the response format as soap message than XML. So, we need to have another WebService as a middleware! Bad day!

Factory.newDocumentBuilder().parse returning DeferredDocumentImpl in servle

With respect to my earlier postregarding servlet not able to print
xml document
In Document parseXMLFile(String filename, boolean b) in servlet the line factory.newDocumentBuilder().parse(new File(filename)); is returning DeferredDocumentImpl
but the same method containing
factory.newDocumentBuilder().parse(new File(filename)); is returning XmlDocument in pain java program
why is the behaviour different
Iam able to print the elements in plain java program but in servlet if i use the same method
iam not able to print anything and returned type
is different and root element iam seeing as nul
could anybody please help
thanks
BHanu

Did the suggestion in http://swforum.sun.com/jive/thread.jspa?threadID=64634 not help?
(That is 'factory.setAttribute("http://apache.org/xml/features/dom/defer-node-expansion", (false));')

Non-English characters processed correctly by XML Parser 2 XSLT?

I'm trying to transform an XML document (parsed as an XMLDocmument) using an XSL stylesheet (parsed as an XSLStylesheet) and the XSLProcessor class in Java, I encounter the following problem:
Non-US characters such as German umlauts, stored in the XML in &#xxx; style, are not processed properly. "|" (ü), for example, comes out as "C<". Is this a bug in the XSLProcessor class or am I doing something wrong? I'm using this stylesheet declaration:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns="http://www.w3.org/1999/xhtml1/strict"> Or should I mess with the encoding attribute of the ?xml ...? PI?
tia
John Smith

I have not specified any encoding.
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="completeproduct.xsl"?>
<PRODUCT connection="demosample" xmlns:xsql="urn:oracle-xsql">
<xsql:query>
select * from products
</xsql:query>
should i specify encoding
null

Verifying and parsing "query" in cm:select query="..." ...

I'm writting a session EJB that's passed a param (String query) which is supposed
to be any valid "query" string passed to the cm:select tag (see "http://edocs.bea.com/wlcs/docs31/p13ndev/jsptags.htm#1057716"
for more info on this tag and the query param).
My problem is this: I don't think I should write ALL the stuff to validate and
parse this string because bea has already done it in: com.beasys.commerce.foundation.expression.*;
but the only source of documentation available on those classes is the Javadoc(which
isn't that complete). Has anyone used these classes before(Search, Expression,
Criteria, Logical)? Does anyone know of some documents on how to use them?
Please help if you can. I'd really appreciate it. Thanks.

rajan please just google or search SDN. there are large number of post for this..
to give you a head start: for using a particular index in the select query a %_HINTS ORACLE 'INDEX clause is added

PARSER UNEXPECTED_VALUE

Similar Messages

Maybe you are looking for