Thanks a million Paul, I will check it out and let you know my progress.
Paul Fremantle wrote:
> Hi
>
> I took your WSDL and ran it through the Eclipse WSDL validator and it
> found a number of bugs. I'm suprised because this WSDL looks like it
> was generated by Axis2. Did you hand edit it after?
Hi
I took your WSDL and ran it through the Eclipse WSDL validator and it
found a number of bugs. I'm suprised because this WSDL looks like it
was generated by Axis2. Did you hand edit it after?
The main problems were namespace problems. I'm not exactly sure what
you were aiming at for namespaces
Hi Paul,
Here is the services.xml
Order processing web service. Currently implemented for
Engen.
za.co.cxchange.soap.business.ConfirmationProcessService
urn:processConfirmation
WSDL
http://schemas.xmlsoap.org/wsdl/soap12/";
xmlns:http="http://schemas.
Hi
Can you please post your complete services.xml. Even better post the AAR file?
Paul
On 12/28/06, schalk <[EMAIL PROTECTED]> wrote:
Greetings All,
First thing I am unclear about is, when clicking on the link on the deployed
services page that should show the WSDL, it gives me the following
Greetings All,
First thing I am unclear about is, when clicking on the link on the deployed
services page that should show the WSDL, it gives me the following result:
If you wish Axis2 to automatically generate the WSDL, then please use one of
the RPC message receivers for the service(s)/operatio
