On Mar 24, 2011, at 11:07 AM, [email protected] wrote: > Hi, > > Filtering urls/dependencies is probably faster than packages, no?
The straight "require xml files" is the fastest, definitely. With a class matching pattern like ".*Bean" it would be even faster. I definitely like this approach as well. The classpath filtering logic as it exists now is pretty slow. Well strictly speaking it's all the built-in excludes we add that are slow. Once you have more than a few regular expressions, evaluating them starts to really cost. We can probably improve that as well. We should be able to reuse the include/exclude logic now in xbean-finder and have it then be completely consistent for filtering classpaths as well as classes. > However i think the ejb-jar approach could still be used/activated by > configuration, it is really a pretty nive feature but it can't be the default > one today, your proposal looks nice as the default behavior. Crossing my fingers it works as well as I hope :) > ----- Reply message ----- > De : "Thiago Veronezi" <[email protected]> > Date : jeu., mars 24, 2011 18:39 > Objet : EJB 3.1 Embedded Container API and the examples > Pour : <[email protected]> > > Hi, David! > Don't you think that a big ugly warning at startup time with some tips to > the user on how to improve the performance can do the job? This way we keep > the "ejb-jar.xml" (I love this one!), the "go through all classes" and the > "by package" approaches. We have some timers and flags in there now. We can keep that and complain about any slowness. As far as ignoring modules that don't have an ejb-jar.xml, we can't do that anymore ... by default at least. We can certainly make it easy to turn on. -David
