Hi Craig! Ok, lets concentrate only on the patch. Please, forget the discussion about speedup, this has nothing to do with the patch.
I do not want to overload CONFIG_FILES nor change its meaning. Say you have a web.xml with the following configuration: javax.faces.CONFIG_FILES=/content/app/conf/faces-config.xml,/content/app2/conf/faces-config.xml The first faces-config.xml is located in myapp.jar and the second one is located in myapp2.jar. Both jars do NOT have a META-INF/faces-config.xml due to the use of javax.faces.CONFIG_FILES shale-tiger ignores those jars due to this fact. The patch do nothing else than to lookup those jars and add them to the list of webArchives. Just for safety I changed the List to a TreeSet. It is possible that such a jar contains a META-INF/faces-config.xml and also some additional special config.xml pointing to with javax.faces.CONFIG_FILES. To not parse them twice is the reason why I changed it to a Set. You see, no special tricks with javax.faces.CONFIG_FILES, nor any other style of class scanning. Ciao, Mario
