Axis2 does not support RPC/encoded[1] apparently because it is not WS-I compliant[2]--they tell their users to stay with the older Axis1 if they must have RPC/encoded. You may wish to consider Axis1 then (which unfortunately will probably create other problems for you.)
Glen [1] http://marc.info/?l=axis-user&m=118807112903325&w=2 [2] http://marc.info/?l=axis-user&m=118579681226453&w=2 Am Mittwoch, den 29.08.2007, 07:53 -0700 schrieb trichter: > HI, > > I ran into the same problem, banging my head at why the Use.ENCODED setting > is not picked up. Does anyone know whether there are plans to include this > capability in CXF? Why would my alternatives be if I needed encoded? > > Thanks. > > > > bmargulies wrote: > > > > CXF doesn't support Encoded. > > > >> -----Original Message----- > >> From: Chris Campbell [mailto:[EMAIL PROTECTED] > >> Sent: Wednesday, August 22, 2007 5:22 PM > >> To: cxf-user@incubator.apache.org > >> Subject: SOAPBinding Use.ENCODED ? > >> > >> I need encoded response, since some of my data has "Illegal > >> character (NULL, unicode 0) encountered" > >> > >> I added > >> > >> @SOAPBinding(style=Style.RPC, use=Use.ENCODED) > >> > >> to my service interface, but the generated wsdl has use=literal, for > >> example > >> > >> <wsdl:operation name="execute"> > >> <soap:operation soapAction="" style="rpc"/> > >> <wsdl:input name="execute"> > >> <soap:body namespace="http://query.soap.quaris.com/"; use="literal"/> > >> </wsdl:input> > >> <wsdl:output name="executeResponse"> > >> <soap:body namespace="http://query.soap.quaris.com/"; use="literal"/> > >> </wsdl:output> > >> </wsdl:operation> > >> > >> Am I missing something? > >> > >> Thanks. > >> > > > > > > >
