Hi All, I have included all the relevant files in this mail. Basically I have below soap message generated using a WSDL generated by AXIS 1.2 RC2 Server. If am planning to use JiBX and may be write custom (De)Serializer on the server side.
Originally request soap message generated by AXIS 1.2 RC2 Client ---------------------------------------------------------------------------------------- <?xml version="1.0" encoding="utf-16"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> <soap:Body> <getDummyBean xmlns="http://ws.as.com/wsdl/typesws";> <VOILA> <j xmlns="http://ws.as.com/schema/typesws";>100</j> <st xmlns="http://ws.as.com/schema/typesws";>ram</st> <i xmlns="http://ws.as.com/schema/typesws";>99</i> </VOILA> </getDummyBean> </soap:Body> </soap:Envelope> WSDL ------ <?xml version="1.0" encoding="UTF-8"?> <wsdl:definitions targetNamespace="http://ws.as.com/wsdl/typesws"; xmlns:apachesoap="http://xml.apache.org/xml-soap"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:impl="http://ws.as.com/wsdl/typesws"; xmlns:intf="http://ws.as.com/wsdl/typesws"; xmlns:tns1="http://ws.as.com/wsdl/typesws"; xmlns:tns2="http://ws.as.com/schema/typesws";> <wsdl:types> <schema elementFormDefault="qualified" targetNamespace="http://ws.as.com/schema/typesws"; xmlns="http://www.w3.org/2001/XMLSchema";> <complexType name="DummyParentBean"> <sequence> <element name="j" type="xsd:int"/> </sequence> </complexType> <complexType name="InputBean"> <complexContent> <extension base="tns2:DummyParentBean"> <sequence> <element name="st" nillable="true" type="xsd:string"/> <element name="i" type="xsd:int"/> </sequence> </extension> </complexContent> </complexType> <complexType name="DummyBean"> <sequence> <element name="i" type="xsd:int"/> <element name="st" nillable="true" type="xsd:string"/> </sequence> </complexType> </schema> <schema elementFormDefault="qualified" targetNamespace="http://ws.as.com/wsdl/typesws"; xmlns="http://www.w3.org/2001/XMLSchema";> <import namespace="http://ws.as.com/schema/typesws"/> <element name="getDummyBean"> <complexType> <sequence> <element name="VOILA" type="tns2:InputBean"/> </sequence> </complexType> </element> <element name="getDummyBeanResponse"> <complexType> <sequence> <element name="getDummyBeanReturn" type="tns2:DummyBean"/> </sequence> </complexType> </element> </schema> </wsdl:types> <wsdl:message name="getDummyBeanResponse"> <wsdl:part element="tns1:getDummyBeanResponse" name="parameters"/> </wsdl:message> <wsdl:message name="getDummyBeanRequest"> <wsdl:part element="tns1:getDummyBean" name="parameters"/> </wsdl:message> <wsdl:portType name="Types"> <wsdl:operation name="getDummyBean"> <wsdl:input message="impl:getDummyBeanRequest" name="getDummyBeanRequest"/> <wsdl:output message="impl:getDummyBeanResponse" name="getDummyBeanResponse"/> </wsdl:operation> </wsdl:portType> <wsdl:binding name="TypesServiceSoapBinding" type="impl:Types"> <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <wsdl:operation name="getDummyBean"> <wsdlsoap:operation soapAction=""/> <wsdl:input name="getDummyBeanRequest"> <wsdlsoap:body use="literal"/> </wsdl:input> <wsdl:output name="getDummyBeanResponse"> <wsdlsoap:body use="literal"/> </wsdl:output> </wsdl:operation> </wsdl:binding> <wsdl:service name="TypesService"> <wsdl:port binding="impl:TypesServiceSoapBinding" name="TypesService"> <wsdlsoap:address location="http://localhost:9999/Proj04022005Axis12Rc2Web/services/TypesService"; /> </wsdl:port> </wsdl:service> </wsdl:definitions> What I am not understanding is how can be write a jibx binding xml and corresponding custom axis (de)serializer that can under this below soap message : <?xml version="1.0" encoding="utf-16"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> <soap:Body> <getDummyBean xmlns="http://ws.as.com/wsdl/typesws";> <VOILA> <j xmlns="http://ws.as.com/schema/typesws";>100</j> <st xmlns="http://ws.as.com/schema/typesws";>ram</st> <i xmlns="http://ws.as.com/schema/typesws";>99</i> </VOILA> </getDummyBean> </soap:Body> </soap:Envelope> In the above soap message, how can we write a jibx binding on the server side for VOILA soap element which happens to be just a wrapper element created by axis but not any actual complex type since as far as my knowledge with jibx goes I can only write binding definitions for complex types but for any wrapper elements in WSDL or is my understanding wrong. I dont want to use any custom (de)serializer (may be on along with jibx) on client side or modify any stubs on client side since I'll be in future giving this wsdl to .NET Client which I expect to generate soap request message that is understandable using my axis server. So I would love if someone can tell what customizations I can do in my WSDL so that I can expect some soap request message using both .NET and AXIS Clients and that is understood by my axis server and generate back a valid soap response message and what how can I write a jibx binding definitions on the server side for VOILA soap element in request soap message. Please suggest .... Thanks & Regards, Kumar. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ jibx-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jibx-users
