Anton, I just looked at the binding again, and realized that it says use="literal" and also specifies encodingStyle. This is not a valid WSDL. You cannot specify an encoding style when use="literal".
Where did you get this WSDL? It would be helpful if you provided us with the complete WSDL. Anne On 4/12/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
The service requires that you send a message encoded using rpc/encoding. Because Axis2 does not support SOAP encoding, you can't use it to build a client for this service. Try Axis 1.4 instead. Anne On 4/11/07, Anton Pirker <[EMAIL PROTECTED]> wrote: > Hi Anne! > > Anne Thomas Manes wrote: > > Axis2 does not support rpc/encoding. > > Does this mean that i can completely forget to implement a client for > the service? > > Or can i just change the binding from rpc to document and everything > will be fine? > (i will try this tomorrow morning in the office, from my home-office i > do not have access to the service) > > > > Anton > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
