i have a web service deployed to axis2 on websphere and the same web service deployed to axis2 on glassfish v2.
the client is a desktop application generated and written in C# using VS2003. the client works well with the service on websphere which it was originally designed for. but not with the service on glassfish. the WSDL generated for both services is exactly the same. i noticed that the response generated from the service on web sphere has the xmlns on every attribute this is not true for the same service on axis2 on glassfish. this is the response message from the service on axis2 on websphere: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> <soapenv:Body> <ns:getPrintJobResponse xmlns:ns="http://myService/xsd";> <ns:return> <bookingRef xmlns="http://myService/xsd";>XXXXXX7730000010001</bookingRef> <jobID xmlns="http://myService/xsd";>209572</jobID> <printerName xmlns="http://myService/xsd";>NAME</printerName> <qty xmlns="http://myService/xsd";>3</qty> </ns:return> </ns:getPrintJobResponse> </soapenv:Body> </soapenv:Envelope> notice that xmlns value appears in all the properties (bookingRef, jobID, printerName, qty). and here is the same response from axis2 on glassfish <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> <soapenv:Body> <ns:getPrintJobResponse xmlns:ns="http://myService/xsd";> <ns:return> <bookingRef xmlns="http://myService/xsd";>XXXXXX7730000010001</bookingRef> <jobID>209552</jobID> <printerName>NAME</printerName> <qty>15</qty> </ns:return> </ns:getPrintJobResponse> </soapenv:Body> </soapenv:Envelope> notice that only the bookingRef has the xmlns my service is a POJO without any annotations. it is wrapped as .aar my questions... A. why is this happening although i'm deploying to a common denominator on both app. servers which is the axis2.war ? B. how do i make the response from glassfish matches the one from webshpere? where do i have to change and what? please note that i can't change he client code so my only bid is to make it work on glassfish as it was working on websphere. -- View this message in context: http://www.nabble.com/axis2-on-webshpere-response-%21%3D-axis2-on-glassfish-response........-why--tp24132443p24132443.html Sent from the Axis - User mailing list archive at Nabble.com.
