It is possible to configure CXFServlet to redirect current requests to other servlets or serve the static resources.
redirects-list init parameter can be used to provide a space separated list of URI patterns; if a given request URI matches one of the patterns then CXFServlet will try to find a RequestDispatcher using the pathInfo of the current HTTP request and will redirect the request to it.
redirect-servlet-path can be used to affect a RequestDispatcher lookup, if specified then it will concatenated with the pathInfo of the current request.
redirect-servlet-name init parameter can be used to enable a named RequestDispatcher look-up, after one of the URI patterns in the "redirects-list" has matched the current request URI.
static-resources-list init parameter can be used to provide a space separated list of static resource such as html, css, or pdf files which CXFServlet will serve directly.
One can have requests redirected to other servlets or JSP pages.
CXFServlets serving both JAXWS and JAXRS based endpoints can avail of this feature.
For example, please see this web.xml .
The http://localhost:9080/the/bookstore1/books/html/123 request URI will initially be matched by the CXFServlet given that it has a more specific URI pattern than the RedirectCXFServlet. After a current URI has reached a jaxrs:server endpoint, the response will be redirected by the JAXRS RequestDispatcherProvider to a "/book.html" address, see "dispatchProvider1" bean here .
Next, the request URI "/book.html" will be handled by RedirectCXFServlet. Note that a URI pattern can be a regular expression. This servlet redirects the request further to a RequestDispatcher capable of handling a "/static/book.html".
Finally, DefaultCXFServlet serves a requested book.html.