…but these things should *not* be loaded via a class path bound getResource API imo.
I don't see a reason to link this to the classpath either. Though, it would be nice to support archives (you'd have to read from a JAR then).
Through extension, it should be possible to load from a directory or the classpath. My point is, just don't hard link it to a classpath location.