when using the uri:classloader: protocol and the lookup can be a directory
then to determine whether it is a directory or not the following sequence takes place

* look for my_directory/.jrubydir and if there use it
* if the url from the classloader is jar url, then see if the jar file
  has a directory entry and use it (zip files may or may not have such
  directory entries depending on how it got packed)
* if url from classloader is file url, then use the file on filesystem and
  check if it is a directory

using ClassLoader.getResources as well URLClassLoader.getURLs for finding directory entries.

…suites

…tions

no more custom url stream handler which some environments do not allow (i.e. java webstart)
and this compound stream handler did work only for jar protocol urls. any custom protocol handler
did not work like the ones from OSGi and some j2ee constainers (wlp, jboss). without the custom
stream handler there is no need to index compound urls

there are no tests for this OSGiScriptingContainer and the last test
did work for felix4 only. no equinox nor knoplerfish no felix3. regular
ScriptingContainer now works with all three osgi frameworks including
embedded gems, etc and has tests for all those frameworks.