Announcement Announcement Module
Collapse
No announcement yet.
HttpInvoker and Axis Web Service Protocol - can co-exist? Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • HttpInvoker and Axis Web Service Protocol - can co-exist?

    I have been able to expose the same service via two different protocols (RMI & Axis Web Service/SOAP) in the same container (Tomcat). Housing all of the code in the axis deployment allows this.

    Now, I am trying to do the same, but having the HttpInvoker co-exist with the Axis Web Service. How Http and Axis handles in-coming requests is not my area of expertise. It appears to me that an Axis servlet is consuming my Http request and not passing on, or allowing it to pass on to the Spring DispatcherSerlvet.

    Any thoughts/comments from the Spring team or anyone else on how to get this to work or if it can work?

    Thanks, in advance.

  • #2
    I did get this to work

    The examples in the books don't really give good examples of how your http url to access the HTTPInvoker based service should be formed. When deployed under Axis, using http://localhost:8080/axis/http/{servicename} is needed. If deployment under tomcat, then http://localhost:8080/{warfilename}/http/{servicename} is used.

    Comment


    • #3
      The usual way to achieve this is to expose different endpoints at different URL paths, with the Axis endpoint managed by the AxisServlet, but all other endpoints managed directly by a Spring DispatcherServlet. A client can then choose which endpoint it wants to talk to, depending on the protocol to speak. Our JPetStore sample application illustrates this.

      Juergen

      Comment

      Working...
      X