[Bug 975] New: Plugin should not include classpaths specified in jar manifests when using jnlp_href

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=975

          Priority: P3
            Bug ID: 975
                CC: unassigned at icedtea.classpath.org
          Assignee: ddadacha at redhat.com
           Summary: Plugin should not include classpaths specified in jar
                    manifests when using jnlp_href
          Severity: normal
    Classification: Unclassified
                OS: Linux
          Reporter: ddadacha at redhat.com
          Hardware: x86_64
            Status: NEW
           Version: unspecified
         Component: Plugin
           Product: IcedTea-Web

You are currently allowed to pass in a manifest to your jars that contains a
Class-Path key-value. Icedtea-Web uses this only if you are running in the
plugin as JNLPs are explicitly documented to not follow Class-Path of a
manifest.

Currently on HEAD, if applets run via jnlp_href have jars with manifests, it
will use the Class-Path if specified. I do not think this behaviour is correct.
If a JNLP is being used as a means of handling the application, IMHO it should
be forced to follow the same restrictions as a webstart app being run via
javaws from terminal.

Currently, the proprietary plugin honours classpaths passed through manifests.
Despite this, I do not think it's the right approach. The point of jnlp_href is
to bridge javaws and plugin, having this difference might throw developers off.
For instance, if one expects that classpaths are ignored from manifests but
includes them (for whatever reason), then running their applet from javaws
would work fine, running it in the plugin with jnlp_href may break if there are
conflicting classes.

To reproduce:
1. Create an applet class and a helper class, each in their own jar. Have the
the manifest of the applet's jar point to the helper's jar.
2. Use a JNLP file with <applet-desc> to run the applet via 'javaws -verbose
$FILE.jnlp'. You should see a ClassNotFoundException
3. Use the same JNLP in a webpage with jnlp_href, it will run fine.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20120501/7873b6de/attachment.html