Comment #2 on issue 636 by [email protected]: Cannot suppress
GuiceFilter warning
http://code.google.com/p/google-guice/issues/detail?id=636
1. Yes.
2. I'm asking what's the impact of this scenario:
Thread1: invoke Guice.createInjector() which invokes
GuiceFilter.setPipeline() indirectly.
Thread1: GuiceFilter.init() invoked, GuiceFilter.pipeline gets read
Thread2: invoke Guice.createInjector() which invokes
GuiceFilter.setPipeline() indirectly.
Thread2: GuiceFilter.init() invoked, GuiceFilter.pipeline gets read
Thread1: invoke doFilter(), which reads Guice.pipeline set by Thread2
Thread1: invoke destroy(), which sets GuiceFilter.pipeline to
DefaultFilterPipeline()
Thread2: invoke doFilter(), which reads Guice.pipeline set by Thread1
etc...
Is there a problem with the fact that Threads are using pipelines set by
other threads?
--
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.
