Hi! I would like to discuss two things which come in my mind during trying out shale-tiger:
1) Speedup of startup While shale-tiger already tries its best to parse only jars with specific markers I think we can further speedup the startup if we allow the user to configure which packages to parse. I think about a context parameter where the user can configure e.g. "org.my.app1.backings,org.my.app2.backings" etc. This will parse classes located within these packages and their sub-packages. There are tricks how to get the classes within an package, I already use such a trick, though, with help from VFS, but it should be backportable to plain java. I know, this is yet another context-param, but the speedup might be worth it. BTW: Having such a configureable framework in commons might be great - or as part of the "web commons" (sorry I've forgotten the name ;-) ) would be great. Any library can register to it and do not need to create all this traversing code itself, but well, we can easily refactor it later .... 2) extension to @View annotation The ViewControllerMapper is responsible to map a view name to the corresponding backing name. Now, with the power of annotations it might be possible to use another approach to map a bean to its view. Say a bean has both annotations, the @View and @Bean, now, if we allow to setup the view name at the @View tag, e.g. @View(name="/to/my/faces/view.jsp") Shale has all informations required to map a view to the bean. "name" should be optional so one can still use the ViewControllerMapper. What do you think? I'll provide patches if you think its useful. Ciao, Mario
