9

I have a use case that required all calls to NewWebService are routed to OldWebService, if the SOAP request does not validate against NewWebService's XSD and WSDL. NewWebService is located on ServerA and OldWebService is on ServerB.

Abstractly, I know I need some mechanism that will allow me to take a SOAP request that hits NewWebService, send it to OldWebService, then return the SOAP result back to the client. My limited experience with spring-ws is making it difficult to decide how to accomplish that.

My first thought was to build a SOAP client into the NewWebService that calls the OldWebService whenever the payload cannot be validated. Is this the best solution, or is there a better way to allow the NewWebService to act as a pass-through for certain requests?

Jared
  • 763
  • 2
  • 7
  • 14
  • There is an option to route requests with WS-Addressing.Refer to [http://static.springsource.org/spring-ws/sites/2.0/reference/html/server.html#server-ws-addressing – Ahamed Mustafa M May 13 '12 at 18:27

2 Answers2

6

My solution was to write a custom SoapRequestFilter that implements a javax.servlet.Filter and a new class that extends HttpServletRequestWrapper. Since HttpServletRequestWrapper implements the HttpServletRequest interface, extending the wrapper allows you to copy the HttpRequest and act on the stream without consuming the object and causing issues downstream.

Once I had the filter and wrapper, I was able to parse the endpoint and payload from the HttpRequest. If the request needed to be redirected, I created a new HttpUrlConnection to the old SOAP WebService and set the InputStream from that response to the OutputStream of the HttpResponse.

Jared
  • 763
  • 2
  • 7
  • 14
0

I think Apache Camel can help you in an efficient way.

You can take a look at its proxy example, it's simple and easy to fulfill your requirement.

http://camel.apache.org/cxf-proxy-example.html

karl li
  • 1,316
  • 15
  • 19