Ales Justin wrote:
but it could be made optional to do this at boot time instead.
The easiest way to do this would be to add a deployer and somesort of weld-lib repository service to the bootstrap process.
e.g. part of bootstrap.xml sub-systems, which would simply take a set of lib locations to check,
and spit out a set of lib jars that contain META-INF/beans.xml -- note, there is no Weld dependency, hence can be easily put into bootstrap
Ales, why should I add it to bootstrap?
I mean, can't I just scan the lib dirs as part of the first weld deployment instead of doing it on bootstrap? What are the advantages of doing otherwise?
Another question: once I determine that a specific jar in lib has the META-INF/beans.xml file, what is the cleanest way of retrieving the corresponding lib ClassLoader?