The Shale Tiger library uses annotations to declare meta-data that in some cases would have been configured using a central XML configuration file.
Shale gathers the annotation data at the startup of the application by loading the classes. Some have expressed concern that loading the classes at startup will not scale well with very large web applications. I was wondering if Shale should provide a maven plug-in that scans the classes before packaging. The Mojo could generate a faces configuration file that is added to the web project before packaging. Or, maybe the plug-in could generate a configuration file that listed the classes containing annotations to process. This would be similar to the JPA out-of-container requirement for entity beans. Any thoughts? Gary
