Posted: Wed May 08, 2013 9:08 am Post subject: javax.xml.bind.UnmarshalException
Novice
Joined: 08 May 2013 Posts: 10
Hi
I am giving detailed description of above topic as i am not able to do so same as above is my first topic.
I am getting below fault code when i am trying to hit a webservice:
Code:
Body
Fault
faultcode:CHARACTER:soapenv:Server
faultstring:CHARACTER:javax.xml.bind.UnmarshalException
- with linked exception:
[javax.xml.bind.UnmarshalException: Unable to create an instance of .miscinfo.v1.MiscInfo
- with linked exception:
[java.lang.InstantiationException]]
detail
Below is my Soap Request:
Code:
SOAP
Body
Below is my SOAP Request in SOAP UI Which is working fine:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmln
<soapenv:Header/>
<soapenv:Body>
</soapenv:Body>
</soapenv:Envelope>
Can any one help me to construct ESQL Statements for the line that are in bold in SOAP Request.
I tried below ESQL Statements and it is giving me above fault code.
[code]
Last edited by rajesh54 on Wed Jan 15, 2014 1:10 pm; edited 1 time in total
Next time please set the code tags around the code segments yourself please.
To the answer. You do define the xml namespace at the tree level but ESQL has no knowledge of this. You also need to define v11 as an ESQL variable of type NAMESPACE like
Posted: Thu May 09, 2013 5:36 am Post subject: javax.xml.bind.UnmarshalException
Novice
Joined: 08 May 2013 Posts: 10
Hi
I tried in various ways of defining namespace and i also defined in the way you specified. It didnt work. I tried by keeping type in coded way and that also didnt worked.
Thanks for your reply and any further suggestion are requested....
If you are struggling to write ESQL that references the fields in your message tree then I can recommend two very useful techniques:
1. Make sure that the message flow project has access to the schemas that describe your message structure. Then use Ctrl-Space in the ESQL editor and let it give you suggestions about how to construct the paths.
2. If you are still getting exceptions, take a debug-level user trace ( requires the use of the command line programs mqsichangetrace, mqsireadlog, mqsiformatlog ) and read the output carefully. It will tell you exactly where the problem is.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum