Comment #8 on issue 369 by [email protected]: Convenient way to expose multibindings and mapbindings from PrivateModules
http://code.google.com/p/google-guice/issues/detail?id=369
In Guice 3, this workaround has another downside. Refer to this: https://code.google.com/p/google-guice/wiki/ToConstructorBindings
"But there are limitations of that approach: manually constructed instances do not participate in AOP."
This implies if I bind to the constructor of an object, I can use AOP on it, even if it's a third-party component.
However, I cannot use this in tandem with the above workaround. If I bind something with a second injector and providers to work around the limitations of the MapBinder/MultiBinder, the objects created by that second injector don't participate in AOP specified in a separate module created for that express purpose. This is a somewhat limiting problem from the perspective of using Guice with AOP.
-- 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.
