Comment #10 on issue 635 by [email protected]: GuiceFilter uses wrong instance of FilterPipeline if used with multiple servlet context and multiple injectors
http://code.google.com/p/google-guice/issues/detail?id=635
It's visible from any subclass of GuiceFilter, so you just need to extend GuiceFilter with your desired strategy for locating pipelines and use that subclass in your web.xml (or wherever you configure the filter-class). Note that the static functionality in the original base class is unchanged, all the subclass affects is the managed/injected functionality.
Note: the patch in issue 618 may well not be the best solution, it's just the simplest solution I've found so far.
-- 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.
