Comment #16 on issue 522 by [email protected]: Servlet forwards from
servlets with pathinfo mishandled
http://code.google.com/p/google-guice/issues/detail?id=522
Assuming the patch is accepted, is there a way to wire in your Forwarding
filter using Guice bindings without web.xml? This is one of the holy grails
of Guice for me; avoiding type-unsafe XML files lying about.
I can't see anything equivalent in Guice-servlets to the <dispatcher/>
element in the <filter-mapping> of a web.xml which would permit you to bind
differently for FORWARD, INCLUDE, REQUEST, ERROR
Perhaps the Forwarding state could be checked in the ForwardingFilter
itself, assuming the host servlet engine is strict on setting the correct
attributes in the request.
javax.servlet.forward.* and javax.servlet.include.* seem to be
the 'namespaces' to check for...
http://java.boot.by/wcd-guide/ch03s05.html
In this way the ForwardingFilter could be wired to handle all requests,
check request attributes and only intervene when necessary, whilst at the
same time an efficiently configured server can bring it in to the chain
only when forwarding or including is actually happening.
--
You received this message because you are subscribed to the Google Groups
"google-guice-dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-guice-dev?hl=en.
