Exposing a binding makes it visible to the containing module and its sibling modules. If you want to expose something nested in two layers of private modules, you need to expose it in once at each level.
Because of awkward interations with JIT bindings, the SPI and multibindings, PrivateModules aren't particularly awesome in practice. Nesting them should work, but it suggests your design is more complicated than necessary. A simpler way to do encapsulation is with package-private classes and regular modules. On my projects we only use PrivateModules when forced to do so. Cheers, Jesse -- You received this message because you are subscribed to the Google Groups "google-guice" 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?hl=en.
