I have a question regarding unwrapped usage of Jibx binding with Axis2
(version 1.1).
Is it possible to make unwrapped document/literal Jibx server side
binding to work with the client, using axis2 XmlBeans implementation?
We compared server responses sent by the XmlBeans binding and Jibx
binding (using identical WSDL file) and saw a slight change in the
content. Basically the only difference presented was the namespace
attribute in XmlBeans response. I would assume we are doing something
wrong in Jibx binding or service deployment... Any idea what is wrong?
Thanks for your help,
Alex
- Jibx:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
<soapenv:Header/>
<soapenv:Body>
<fetchRequestResponse
xmlns:app="http://dm.ppm.mercury.com/xsd";
xmlns="http://dm.ppm.mercury.com/xsd";>
<fetchRequestReturn
xmlns="http://dm.ppm.mercury.com/xsd";>
<requestType>Bug</requestType>
<identifier>url1</identifier>
</fetchRequestReturn>
</fetchRequestResponse>
</soapenv:Body>
</soapenv:Envelope>
- XMLBeans:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
<soapenv:Header/>
<soapenv:Body>
<fetchRequestResponse
xmlns="http://dm.ppm.mercury.com/xsd";>
<fetchRequestReturn>
<identifier
xmlns="http://types.dm.ppm.mercury.com/xsd";>url1</identifier>
<requestType
xmlns="http://types.dm.ppm.mercury.com/xsd";>Bug</requestType>
</fetchRequestReturn>
</fetchRequestResponse>
</soapenv:Body>
</soapenv:Envelope>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users
