[jbossws-dev] [Design of JBoss Web Services] - Re: RM Sender/Receiver as High Available (HA) Components

First identified problem is HA itself. Imagine the following usecase: Client sends WS-RM message to a webservice endpoint that is not available. The default AS behaviour in such case is 404 (resource N/A). To overcome this problem here are the potential solutions that comes into my mind: 1) Deploy a special servlet that would do the following steps: * will match all http(s) requests that would result in 404 on running AS instance (is it doable?) * will ignore all http(s) POST requests that wouldn't contain SOAP envelope with WS-RM 1.0/1.1 protocol elements (quite performance issue but realizable) 2) Deploy a special servlet that would do the following steps: * will reside on /wsrm/* web context * all "GET WSDL" http(s) requests would return a modified WSDL document to reference the endpoint using /wsrm prefix for web context. (Of course only if such WSDL exists - otherwise it would return 404.) Example: | | client request GET .../wsrm/ctx/endpoint?wsdl | special servlet request GET .../ctx/endpoint?wsdl | RETURN modified WSDL or 404 (if above WSDL isn't available) | * will ignore all http(s) POST requests that wouldn't contain SOAP envelope with WS-RM 1.0/1.1 protocol elements (quite performance issue but realizable) For both above approaches it is supposed to use ServletContext.getContext() method to gain access to the context for various parts of the server, and as needed obtain RequestDispatcher objects from the context. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126210#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...