[ http://issues.apache.org/struts/browse/SHALE-295?page=comments#action_38298 ] Craig McClanahan commented on SHALE-295: ----------------------------------------
So, in other words, you propse to analyze *all* jars in the webapp, whether or not they contain a META-INF/faces.config.xml resource? To me, that sounds like a total non-starter. Consider an app that includes Hibernate and all its dependency jars. What possible benefit can be gaiined by scanning all of those JARs at startup time? Indeed, for such an appliation, having to pay any attention to such a jar (to test whether it contains any classes in the package list specified as an init parameter) is pretty much guaranteed to make startup time *worse* instead of better. Indeed, it was this kind of use case that led to the optimization to scan classes only for JARs that actually had a META-INF/faces-config.xml resource in the first place. > collect web archives with explicit configured faces-config.xml pointing to > them > ------------------------------------------------------------------------------- > > Key: SHALE-295 > URL: http://issues.apache.org/struts/browse/SHALE-295 > Project: Shale > Issue Type: Improvement > Components: Tiger > Reporter: Mario Ivankovits > Attachments: explicit_jars.diff > > > The patch will also collect jars in WEB-INF/lib which have a faces-config.xml > pointing to them through the configuration javax.faces.CONFIG_FILES > That way, you no longer need to have a "marker" faces-config.xml in META-INF. > The patch is not heavily tested yet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
