Charles Caldarale recommended UrlRewriteFilter and after experimenting with
it, I agree it's very nice: great performance, very flexible and handles
cross-context forwarding. The custom Valve option is still attractive
because it has slightly better performance, slightly better cross-context
chuck.caldar...@unisys.com wrote:
If you place the standard rewrite filter in the ROOT context, you can catch
any requests that do not directly map to the appropriate webapp and forward
or redirect them appropriately.
I looked at UrlRewriteFilter and it seemed designed for forwarding within
Ken Fox wrote:
chuck.caldar...@unisys.com wrote:
If you place the standard rewrite filter in the ROOT context, you can catch
any requests that do not directly map to the appropriate webapp and forward
or redirect them appropriately.
I looked at UrlRewriteFilter and it seemed designed for
From: Ken Fox [mailto:k...@vulpes.com]
Subject: Re: Mapping REST requests across multiple app contexts
I looked at UrlRewriteFilter and it seemed designed for forwarding
within a context, not between contexts.
Not true; forwards may cross contexts - look at the context attribute
I'm looking for advice on the best way to map REST requests onto a
collection of Tomcat apps all running in the same JVM. The REST name space
was designed for client use and doesn't reflect how the apps implement it.
For example, the resource /v1/x/123 is implemented by app X, but the
resource
From: Ken Fox [mailto:k...@vulpes.com]
Subject: Mapping REST requests across multiple app contexts
I'm trying to implement the rewrite as a Valve
If you place the standard rewrite filter in the ROOT context, you can catch any
requests that do not directly map to the appropriate webapp
