Hi Dennis, Thanks for the reply. I tried to work with new jars and the xml did not change. So I'm thinking may be it is a mapping problem or wsdl problem. In the wsdl we have two schemas with different namespaces defined, one schema defines parameter types and the other has responses and messages. So I'm attaching those and may be, if you have time, you will be able to spot a potential problem somewhere.
Thanks for your help, Alex Mapping excerpt: <binding force-classes="true" xmlns:tns="http://types.dm.ppm.mercury.com/xsd";> <namespace uri="http://types.dm.ppm.mercury.com/xsd"; default="elements"/> <mapping abstract="true" class="com.mercury.ppm.dm.types.Request" type-name="tns:Request"> <value name="requestType" style="element" field="requestType" usage="optional"/> <value name="identifier" style="element" field="identifier" usage="optional"/> </mapping> </binding> WSDL excerpt: ... <wsdl:types> <xs:schema xmlns:ax21="http://types.dm.ppm.mercury.com/xsd"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://types.dm.ppm.mercury.com/xsd";> <xs:element name="Request" type="ax21:Request"/> <xs:complexType name="Request"> <xs:sequence> <xs:element name="identifier" nillable="true" type="xs:string"/> <xs:element name="requestType" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:schema> </wsdl:types> .... <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns:ns0="http://types.dm.ppm.mercury.com/xsd"; attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://dm.ppm.mercury.com/xsd";> <xs:element name="fetchRequest"> <xs:complexType> <xs:sequence> <xs:element name="param0" nillable="true" type="ns0:Identifier"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="fetchRequestResponse"> <xs:complexType> <xs:sequence> <xs:element name="return" nillable="true" type="ns0:Request"/> </xs:sequence> </xs:complexType> </xs:element> ---------------------------------- Hi Alex, There were some errors in the Axis2 1.1 unwrapped handling for JiBX, especially around namespaces. I've just dropped the latest code at http://www.sosnoski.com/jibx-wiki/space/axis2-jibx - try it out and let me know how that works for you. And yes, JiBX server side with XMLBeans client side should be no problem, as long as the JiBX code is working properly and the binding is correct. - Dennis Dennis M. Sosnoski SOA and Web Services in Java Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117 -----Original Message----- From: Alexander Grivnin Sent: Monday, December 04, 2006 7:34 PM To: 'jibx-users@lists.sourceforge.net' Subject: Jibx with Axis2 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
