Comment #6 on issue 618 by davidb...@gmail.com: Make guice-servlet more adaptable
http://code.google.com/p/google-guice/issues/detail?id=618
This issue really needs to be fixed. As comment 5 states, with the October 2011 changes, making FilterPipeline public and the GuiceFilter(FilterPipeline) constructor visible (ideally public, but protected is workable as well) is sufficient.
The JVM-scope staticness (actually, classloader-scope staticness) of GuiceFilter is a real blight on the library. The code is in place to not rely on it accept for backwards compatibility (i.e., dynamic filterpipelines are supported; the constructor is just not visible). Please make it visible.
-- You received this message because you are subscribed to the Google Groups "google-guice-dev" group. To post to this group, send email to google-guice-dev@googlegroups.com. To unsubscribe from this group, send email to google-guice-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-guice-dev?hl=en.
