Comment #34 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
The problem isn't multiple contexts. The problem is unit tests, where you
might have multiple servers, each instantiating their own GuiceFilter, but
they are all running inside the same Classloader.
I tried asking both JUnit and TestNG authors to add Classloader isolation
and they both refused claiming this would degrade performance and cause
annoying casting problems.
So, here we are.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
"google-guice-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-guice-dev.
For more options, visit https://groups.google.com/d/optout.
