Hi, I'm writing some Design pattern for guice modulling, and some point puzzles me:
I want to have a module (A) that depends on a service S ( let say a database session manager). moduleA is not my main module, and therefore I don't want to bind the service S to any actual classes. (kind of "abstract" module). I my code, in introduce injection point to the service S, and I expect that those bindings will be satisfied in the "real app". When it's the case, everything works fine. But I would like to "declare" within moduleA that it "requires" S. So that consumers of my ModuleA knows that they need to provide a binding for the serviceA. My concern is that actually the injection point is hidden somewhere in the whole code, and it won't appear until Runtime. Application construction team have no mean to be aware of this "required" service that hey must bind. Is there a way to declare this "required" binding ? is there a way to see it (using graph for instance) ? is there a possibility to "check" a module for binding "correctness" ( there is no "unwired" keys) thank you -- 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.
