Implementation of review comments for classpath and jar

resourceFactories
This still looks too much like the super class implementation.  The only difference I see (other than variableNames) is the use of 'jar' vs 'classpath' (can use getScheme() instead) and the bit at the end where you use resolve to get the new instance if finalFileUri is null.  Why is this check needed for JarResource but not for ClasspathResource?  Is an exception thrown while processing JarResource.resolve() expected under normal conditions but not so for ClasspathResource:resolve().  Anyway, it seems to me that the same code could be in the base class implementation as well.  So that means that there really is no difference between the two, and with the use of getScheme() instead of hard-coded strings, there would be no reason to override this method.