title: OneJar and dynamic class loading
body: <p>We're currently investigating the use of OneJar in our application (for a number reasons), but our application makes use of a number of custom <code>URLClassloader</code>s to load application extensions.</p>
  
  <p>When bundled as a "OneJar" Jar, we get <code>ClassNotFound</code> exceptions.  The classes in question reside in the bundled Jar and we are simply relying on the classloader mechanism to resolve the parent/child relationship.</p>
  
  <p>That is.  We have a common <code>interface</code> which is stored in the bundled Jar (which should be the within the parent's classloader context).  The extension implements this <code>interface</code> (allowing us to call into the extension) and relies on the ability of the child classloader to use the parent classloader's resource finding capabilities.</p>
  
  <p>Has any one had any experience with this or shed any light on how we might go about resolving it.</p>
  
  <p>I'd be interested in other similar mechanisms (for bundling our library Jar's into a single Jar resource, that doesn't require use to unjar everything and Jar into a single file)</p>