If not one has seen the problem I have below, can at least get some
pointers as to where
I can find client samples for remote POJO Axis2 services running in
Tomcat? The documentation
does not include such code (unless the client listed that uses the same
technique of sending and
receiving OMElements can also be used in this case).
With Axis 1.4 we got used to generating stubs and importing them in our
services - calls to them
were what was needed to access the remote service. How much of the
stubs/proxy model is used
in Axis2?
Thanks again
Demetris wrote:
Hi all,
this is the simple POJO service I deploy on Tomcat/Axis - why it is
complaining about an EPR and a WSA Action
when according to the user guide there is no where noted that these
should be said in the code. I did setup the services.xml
as outlined in the guide - any ideas??
Thanks much
INFO: Server startup in 2331 ms
[ERROR] The endpoint reference (EPR) for the Operation not found is
/axis2/services/BooksAxis2 and the WSA Action = null
org.apache.axis2.AxisFault: The endpoint reference (EPR) for the
Operation not found is /axis2/services/BooksAxis2 and t
he WSA Action = null
at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:89)
at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
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.util.RESTUtil.invokeAxisEngine(RESTUtil.java:135)
at
org.apache.axis2.transport.http.util.RESTUtil.processXMLRequest(RESTUtil.java:84)
at
org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processXMLRequest(AxisServlet.java:827)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:215)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
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:191)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
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:298)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
at java.lang.Thread.run(Thread.java:595)
Demetris wrote:
Hi all,
I am testing legacy WS modules that were running well on Axis 1.4.
In essense with minimal changes I have been able to deploy these
services
on Axis2 1.5 in Tomcat. I can retrieve their WSDL docs the same way I
did
with Axis 1.4. However, I am noticing that simple clients that
generated SOAP
messages to access the services do not work unmodified with the
services deployed
in Axis2 - this is normal I assume? Or should Axis2 be able to handle
this correctly?
I also noticed that the WSDL of the POJO services in Axis 1.4 has the
following
namespace in the PortType - something that is non-existant in the
WSDL when
the service is deployed in Axis2:
<wsdl:operation name="getBooks">
<wsdlsoap:operation soapAction=""/>
-
<wsdl:input name="getBooksRequest">
<wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="http://myBooks2"; use="encoded"/>
</wsdl:input>
Not usre if this is relevant but I have a feeling it is- if the
result that simple clients cannot
be used for both Axis 1.4 and Axis2 on the same POJO service then
that answer my
questions - but can someone with more knowledge of this verify it?
Thanks
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
