Thank you Maarten for pointing out the documentation I wrote on this. In my project, I have 60+ jar files in the classpath and the scan only took 255 milliseconds (on a 1.66 ghz core duo mac).
Initializing hibernate takes much longer. I think this is pretty decent, and since it is only incurred at startup, we don't require an alternate solution. Also note that anything JAR-based would not easily work in development environments where you don't JAR after each change. -Doug Maarten Bosteels wrote: > > On Wed, May 7, 2008 at 9:20 AM, Johan Compagner <[EMAIL PROTECTED]> > wrote: > >> if the scanning of the classpath is expensive (i guess all classes are >> loaded that are scanned..) > > > Hi, > > I guess you haven't read the docs completely :-) > > It says: "Note that Spring does not load the class to determine this > information. Instead, it uses a meta-data reader to determine this (which > is > faster than going through class loading)." and also: "The class path > scanning is very efficient by itself and limiting the search only makes it > faster." > > regards, > Maarten > > >> >> cant there be an option that the scanning is only done once? >> When you create the jar so with maven/ant? >> When creating the jar you are scanning everything and create a manifest >> entries of all the packages. >> those manifest entries are then read in when the jar is in the classpath >> >> johan > > -- View this message in context: http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-tp17090601p17103504.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
