Comment #35 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
I have a valid use case, where this issue proved to be troublesome. I
applied the current patch presented here and it worked.
Having applications A and B, both packed as EAR having EJB's. Both have
Guice DI, provided by GWTP.
Both applications have it's own instances of the GuiceFilter.
I tried adding A's EJBs classes to the /lib folder of the the B
application, but invoking the EJB proved to be unsuccessful, because of the
classloading issues. FooEJB from A project wasn't the same as the FooEJB at
the B project /lib folder.
I removed the A application from the /lib folder of the B project and
deployed as a dependent module (on JBoss 7.20). Now the B project shares
the EJB classes from A project, but also the GuiceContext. Issues when I
tried load a A application URL and B GuiceFilter would "intercept" and try
to process it. EJB worked fine.
Refactoring A application common classes would work, but that would be too
much work (big blob of legacy code), patching was simpler. Patched worked
on Guice 4.
--
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.
