Hi Jose , Please have a look at Axis2 1.3 RC1 release , I think we have fixed the issue there.
http://people.apache.org/~deepal/axis2/1.3-RC1/ Thanks Deepal > Hi, > > - I'm using Axis2 1.2 > > I've create a POJO test web service that resides in package > dev.axis2.ws.service and uses in/out bean data from package > dev.axis2.ws.data. > > The interface is: > > package dev.axis2.ws.service; > > import dev.axis2.ws.data.InputData; > import dev.axis2.ws.data.OutputData; > > public interface TestService { > public OutputData testData(InputData input); > } > > 1) When I use automatic wsdl generation from Axis (in the services.xml > file) all goes well. Here is the SOAP response of the execution: > > <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";> > <soapenv:Body> > <ns:testDataResponse xmlns:ns="http://service.ws.axis2.dev/xsd";> > <ns:return> > <data xmlns="http://data.ws.axis2.dev/xsd";>datos de entrada</data> > </ns:return> > </ns:testDataResponse> > </soapenv:Body> > </soapenv:Envelope> > > 2) Things goes wrong when I use the parameter useOriginalWsdl in the > services.xml file. Here the services.xml file: > > <service name="TestService"> > <messageReceivers> > <messageReceiver > mep="http://www.w3.org/2004/08/wsdl/in-only"; > class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver" /> > <messageReceiver > mep="http://www.w3.org/2004/08/wsdl/in-out"; > class="org.apache.axis2.rpc.receivers.RPCMessageReceiver" /> > </messageReceivers> > <parameter locked="false" > name="ServiceClass">dev.axis2.ws.service.TestServiceImpl</parameter> > <parameter locked="false" name="useOriginalwsdl">true</parameter> > <parameter locked="false" > name="modifyUserWSDLPortAddress">true</parameter> > </service> > > The SOAP response I receive in the client side is: > > <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";> > <soapenv:Body> > <ns:testDataResponse xmlns:ns="http://service.ws.axis2.dev/xsd";> > <ns:return> > <ns:data>datos de entrada</ns:data> > </ns:return> > </ns:testDataResponse> > </soapenv:Body> > </soapenv:Envelope> > > In this case the namespace for the data element (it should map to > http://data.ws.axis2.dev/xsd) is missing and the client throws and > Unexpected subelement exception. > > I have tried: > > - Axis2 1.2 > - Axis2 1.1.1 > - Axis2 last snapshot > - Using the wsdl generated automatically > - Using the wsld generated by axis2 tools (ant task and by command line) > > In all cases the behavior is the same: Unexpeted subelement and the > missing namespace in the response message. > > Could you help me please? Thanks in advance! > > Jose Luis > > > ------------------------------------------------------------------------ > > Sé un Mejor Amante del Cine > ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! > <http://us.rd.yahoo.com/mail/es/tagline/beabetter/*http://advision.webevents.yahoo.com/reto/entretenimiento.html>. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
