This week's book giveaway is in the Agile and other Processes forum. We're giving away four copies of The Mikado Method and have Ola Ellnestam and Daniel Brolund on-line! See this thread for details.
How to call Axis2 Webservice from another web service
Vijay Narula
Greenhorn
Joined: Feb 11, 2011
Posts: 5
posted
0
When an Axis2 web service is called from an Axis2 web service, the receiving web service throwing this error:
Could anyone be able to do this, calling a webservice from another webservice? I couldn't seem to find any information
on the net how to do this? Any help would be greatly appreciated.
[WARN] triggerActionNotSupportedFault: messageContext: [MessageContext: logID=urn:uuid:06A6978B9EEDDC2C371302796220340] problemAction: urn:anonOutInOpResponse
[ERROR] The [action] cannot be processed at the receiver.
org.apache.axis2.AxisFault: The [action] cannot be processed at the receiver.
at org.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingFault(AddressingFaultsHelper.java:373)
at org.apache.axis2.addressing.AddressingFaultsHelper.triggerActionNotSupportedFault(AddressingFaultsHelper.java:336)
at org.apache.axis2.dispatchers.AddressingBasedDispatcher.checkAction(AddressingBasedDispatcher.java:141)
at org.apache.axis2.dispatchers.AddressingBasedDispatcher.invoke(AddressingBasedDispatcher.java:126)
at org.apache.axis2.engine.Phase.invoke(Phase.java:318)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:142)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:637)
Ulf Dittmer
Marshal
Joined: Mar 22, 2005
Posts: 35247
7
posted
0
A web service is just a Java class (or several) - there's no particular difficulty in integrating a client to some other WS in it.
How did you integrate the client classes for the second WS in the classes that implement the first WS?
Ulf Dittmer wrote:A web service is just a Java class (or several) - there's no particular difficulty in integrating a client to some other WS in it.
How did you integrate the client classes for the second WS in the classes that implement the first WS?
In the first WS code calling the second WS, I integrated using the Operation Client API (the same code that work perfectly as the stand-alone client)
Vijay Narula
Greenhorn
Joined: Feb 11, 2011
Posts: 5
posted
0
Ulf Dittmer wrote:A web service is just a Java class (or several) - there's no particular difficulty in integrating a client to some other WS in it.
How did you integrate the client classes for the second WS in the classes that implement the first WS?
Anyone?
Have you actually tried a very simple one to see if it works? I googled on the internet and can't seem to find a solution.
thanks,
Ulf Dittmer
Marshal
Joined: Mar 22, 2005
Posts: 35247
7
posted
0
I have; it works.
If this was my problem I'd start by using an HTTP monitor to observe how the HTTP/SOAP message differs between a desktop app acting as WS client and a WS acting as the WS client.