Comment #2 on issue 618 by [email protected]: Make guice-servlet more adaptable
http://code.google.com/p/google-guice/issues/detail?id=618
Basically we have multiple injectors (each one with servlet modules) and every injector should participate in filtering/serving up content. So any incoming request should be passed onto each injector pipeline in turn, finally delegating to the static web.xml (ie. much like the single injector case, but abstracted over multiple injectors).
So 1) we want to (re)set the injected pipeline in the GuiceFilter subclass to use our chained implementation
... and 2) we want to provide our own implementation of FilterPipeline, so we need access to the interface
This is the cleanest way we've found to use guice-servlet in a multi-injector scenario.
-- 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.
