I'm thinking about using CDI/Weld as the DI container for the internal classes of a framework that will be used by a number of applications. The applications may, or may not, use CDI for their own DI. How can I minimize the cross-talk between the framework and application when both are using CDI?
(Ideally, I would be able to say that the framework classes shouldn't bind to stuff outside the framework jar, and not allow classes outside the framework jar to bind to framework classes. Is this possible?)
bump
(Or please tell me if I'm not making sense, it's the wrong question to ask, or if doing what I ask is just really really hard ;-)