Re: No such operation error using document/literal service

n the WSDL??? PrderIdentification should be OrderIdentification i think. stephen DealRaider.com wrote: Thanks for the response. I tried changing the URN to have '.' in place of the '\' but I get the same err

Re: No such operation error using document/literal service

Thanks for the response. I tried changing the URN to have '.' in place of the '\' but I get the same error. Anybody have another idea? DealRaider.com wrote: Hello, Thanks to slight hints in previous responses, I think I am now able to better explain my current

No such operation error using document/literal service

Hello, Thanks to slight hints in previous responses, I think I am now able to better explain my current issue: I have a pre-specified WSDL document I'm creating a new Web Service for. It specifies a doc/literal type style. I've attached the full WSDL, and also list here some of the key exce

Re: Operation name being changed to parameter in SOAP

If this is the correct SOAP that should be sent, why does Axis report the error: No such operation name: "x_GetOutstandingOrders" There is no operation named that, it is named GetOutstandingOrders. DealRaider.com wrote: Hello, After installing the now-final JBoss 3.2.2 wit

Operation name being changed to parameter in SOAP

Hello, After installing the now-final JBoss 3.2.2 with embedded Tomcat and redeploying Axis, I'm appearing to get cleaner error messages. For now, I have a strange situation where the SOAP that is going on the wire is improperly formatted. It's not specifying the operation to call, only the

Error trying to do typemapping and deploy

Hello, I'm fairly new to Axis, and thought I had figured it out until I got to the typemapping. Since I have been unable to find a DTD/XSD for the WSDD file, I've had to try and use others' examples. This has consumed 10+ hours of my day now, so I would greatly appreciate any help. Please r