[Bug 3587] javaws add all JAR files embeeded inside JNLP references JAR file to the JNLP classpath

[bugzilla-daemon at icedtea.classpath.org]

https://icedtea.classpath.org/bugzilla/show_bug.cgi?id=3587

--- Comment #6 from JiriVanek <jvanek at redhat.com> ---
(In reply to Robert Marcano from comment #5)
> (In reply to JiriVanek from comment #3)
> > Thank you for reproducer.
> > So the complain is that nested jars *are* on jnlpcalssoader's classapth? 
> > But that is correct behaviour.
> 
> Sorry, from where do you get that embedded JARs added by default to the
> classpath to be correct behaviour? Oracle implementation doesn't do that,
> Never found a reference to that on the small JNLP spec


Straight to the heart.  That was included in 2009
(http://icedtea.classpath.org/hg/icedtea6/file/46128f71ec57/rt/net/sourceforge/jnlp/runtime/JNLPClassLoader.java)
so from my point of view "that  was always there so it is right".

I'm really surprised that oracle jre do not do it. Maybe they were doing it,
and later they abandoned that, because ITW is trying to mimic proprietary
javaws in both features and bugs, so it is compatible.

I doubt that this changed was added by random.   I emiale doriginal author,
maybe he will remember.

During my own involvement in ITW I met many applications which relied on nested
jars being  on jnlpclasslaoder classpath.  That says, I never doubted itw is
handling nested jars incorrectly. If oracle javaws dropped this support, I'm
wondering why.

-- 
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/20180514/fc107224/attachment.html>