0 Replies Latest reply on Mar 28, 2006 11:41 AM by Oliver Dungey

    java2ParentDelegation problems with JNLP/webstart?

    Oliver Dungey Newbie

      I am running JBoss 4.0.3 SP1. I have an EAR file and within the EAR file I have a couple of WAR files. One of the WAR files contains all our JNLP/webstart applications and these all work fine using the Java 1.5 JnlpDownloadServlet.

      In order to remove duplication of JAR's within our installation I moved many of our JAR's out of the WAR and into the parent EAR file. To support this I added a jboss-app.xml file to the META-INF directory of the EAR containing:

      <jboss-app>
      <loader-repository>
      mycompany.com:loader=SomeUniqueName
      <loader-repository-config>java2ParentDelegation=true</loader-repository-config>
      </loader-repository>
      </jboss-app>

      I also added a jboss-web.xml file to my WAR file in the META-INFO folder like this:

      <jboss-web>
      <class-loading java2ClassLoadingCompliance="true"/>
      </jboss-web>

      Using this configuration I debugged through the JnlpDownloadServlet and found that my WAR file can see the classes in the EAR with no problem but the HttpServletContext object that is used by JNLP to loadResources for downloading to clients fails to see any files outside of the WAR so the JNLP applications fail to start with missing JAR's.

      After much searching I have come up with no ideas of how to get webstart/JNLP to reference files in the parent EAR for downloading to clients.

      I found this article from Sun http://java.sun.com/j2ee/verified/packaging.html and tried out the section "Mechanism 2: Bundled Optional Classes" and added a line "Class-Path: my.jar" into my MANIFEST.MF file but this didn't do anything either.