I have a client that runs from main that calls a thirdparty web service from a stub generated from the wsdl.
Making a call this way works fine.
I have another client within a deployed web application (i.e. 0c4j) that uses the same stub but returns a org.apache.axis2.AxisFault: Transport error: 501 Error: Not Implemented
after the _operationClient.execute(true); within the stub. I have checked the soap package within the stub for both calls before it goes out and they are both the same.
Not sure why it works from main and yet fails within the application server.
posted 8 years ago
Hi I'm pulling my hair out with this one (i.e. whats left of it), can anybody help.
thanks for getting back to me. The same generated axis2 code (i.e. wsdl2java) is being used by both the deployed application and the standalone application.
My initial attempt was to get the connection working with the third party service, via the generated stub. I created a simple standalone app that just called the webservice
(i.e. logged on via a login operation using an encrypted password). Everything looked ok until I tried to do the same within a web application that I deployed into a local oracle server 10.1.3(oc4j).
The deployed war contains the same generated axis2 code as used by the standalone application. I have a spring quartz schedular that calls a class within the deployed app so that the app can logon to the third party web service and the carry out any other operations. I have looked inside the generated stub and the soap package is the same for both. The third party web service has been installed within our intranet. I'm not sure if this is some sort of proxy problem that is causing this error. Is the way that a standalone app communicates with a webservice different to that inside a deployed web application?, Can standalone applications also hit proxy servers?. Soory for the questions but I'm hitting a blabk wall with this.
(i.e I can access the third party wsdl via the browser)
posted 8 years ago
have you been able to find out what is causing this fault.