> > if the scanning of the classpath is expensive (i guess all classes are > > loaded that are scanned..) > > 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."
Deep down it does scan the class path though, in a very similar way as we do in some parts of Wicket. I don't know much about ASM (which is used by Spring to visit the class definitions). Is that where you get the edge in performance? Anyway, I'm not sure whether you actually need Spring (and) ASM to do the trick, but it does look quite nice, both the Spring code and how wicketstff-annotation does it. Cheers, Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
