2009/1/7 Mario Ivankovits <ma...@ops.co.at>: > >> -----Original Message----- >> From: Jan-Kees van Andel [mailto:jankeesvanan...@gmail.com] >> Sent: Wednesday, January 07, 2009 8:15 AM >> To: dev@myfaces.apache.org >> Subject: Re: Scanning for annotated classes in MyFaces 2 >> >> It might be smart to put this Shale code in a separate project. For >> example >> in Commons, since there are several Apache projects that need to scan >> for >> annotations, like EJB3 and JPA projects. > > > Yeah, I thought the same too. > What would be great would be some sort of "annotation scanner" where you can > register a "scanning job" for system startup so that the classpath scanning > has to take place only once and the scanning jobs get called back about the > results. > > Sure, if a scanning job registers something like "**" all packages get > scanned and startup time is slow again, but this is on the responsibility of > the developer then. > > > I can help to startup a commons sandbox project and to work out a > specification for the library, but my spare time for coding is very low :-( > > Ciao, > Mario > >
Mario, I've been looking at the Shale code that handles the annotation scanning, but I saw it uses Reflection and standard Java ClassLoaders for scanning the classpath for JSF artifacts. What's your experience with the performance of this? Does Shale heavily rely on specifying a base package to be efficient? /Jan-Kees
