Load JAR resources via classpath

[jchafik]

Currently, JarLocator converts the JAR location to a URL based on the client request URL. This is inefficient and introduces the possibility of other errors.

Additionally, when there is an error, JarLocator sets neverFail to true, forcing the request to silently fail.

A few issues with the current configuration:

• The URL may be served on HTTPS. If SSL is misconfigured, Java is by default more intolerant than most clients. This can include an incomplete certificate chain or SNI issues.
• Outbound traffic may be restricted by a firewall
• An entire HTTP cycle is required to fetch an asset (longer if SSL is introduced), opposed to a few I/O operations on the filesystem otherwise.

[tduchateau]

You're right! Thanks for pointing this out.