[ http://issues.apache.org/struts/browse/SHALE-295?page=comments#action_38296 ] Mario Ivankovits commented on SHALE-295: ----------------------------------------
Well, call it "wrongly packed" or simply "somehow different", but not all jar files contain a META-INF/faces-config.xml. Instead, one configure the faces-config.xml through the context parameter CONFIG_FILES, something like: CONFIG_FILES=/my/webapp/conf/faces-config.xml,/my/webapp2/conf/faces-config.xml (That way you also can turn on/off a "behaviour" by simply editing web.xml instead of copying/removing a jar around) Now, for sure, you can also put a empty faces-config.xml in the jar, but, on the other hand it is also possible to lookup in which jars the faces-config.xml lives and add them to the list of webArchives. This is what the (simple) patch do. It checks the location of the CONFIG_FILES, and, if its a jar, add it to the list of webArchives. There is no discussion on the mailing list as I needed it for our application and though it would be a good idea. I thought, that this is just the last puzzle in figuring out which jar contains a faces application. > 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
