Ales Justin wrote:
Why the rush? :-)
If you ask me, I would do it lazily aka on_demand.
Scanning the whole common/lib is gonna be slow,
and imo, people should not be using libs to deploy Weld components -- simply put them in deploy/.
Or why would you do it upfront?
I've been thinking about correctness all this time. If somebody places a jar in lib and expects that the beans are created upfront when AS starts, then this would not work using your approach.
Thinking about performance, though, I think that we should trade that by better performance, i.e., we should use the suggested lazy approach.
And I don't see any useful scenario where somebody would want to have a bean deployed to lib dir loaded at startup, specially if no other bean deployed in deploy dir has a dependency towards it.
Pete, does the lazy approach fullfills the Weld prerequisites regarding lib jars?