[Bug 3350] Java applet launched via jnlp web-start cannot load. Fails with "Could not initialize applet"
bugzilla-daemon at icedtea.classpath.org
bugzilla-daemon at icedtea.classpath.org
Thu Apr 6 12:27:13 UTC 2017
http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=3350
--- Comment #13 from stefan at kemtrak.com ---
See below
(In reply to JiriVanek from comment #8)
> ...
> >
> > Was the jnlp file any help?
> >
>
> yes!
>
> > > >
> ...
> > > Still, may you please verify it helped?
> >
> >
> > OK, I have created the file deployment.properties in ~/.config/icedtea-web/
> > with the following content.
>
> ty!
>
> >
> > #Netx deployment configuration
> > #Wed Apr 05 12:51:00 CEST 2017
> > deployment.manifest.attributes.check=NONE
> >
> > I got exactly the same error as before. But
> >
> > Then I tried adding
> > deployment.security.level=ALLOW_UNSIGNED on a second try.
> >
> > That made the main class load for the first time! But it didn't load the
> > rest of the classes contained in the jar files and it was left hanging at
> > what I have as boot screen.
>
> this is very starnge. Do you mind to verify even with cleared cache? (javaws
> -Xclearcache)
Yes, nice you mentioned that, it can be very confusing with caching. I will
from now on clear the cache between any run to make sure.
I can report that with clean cache the results are slightly different. This
time Today I have also ran multiple times each experiment to make sure. So:
With *none* of the
1) deployment.manifest.attributes.check=NONE
2) deployment.security.level=ALLOW_UNSIGNED
I get the initial bug report - nothing loads
With just nr.2 activated, main class loads but nothing else
Different than yesterday: With just nr.1 activated, now - main class loads
again but nothing else. Yesterday this did not happen, I guess probably because
it ran a cached version.
Unfortunately I can't really say I understand the results. But I hope it helps
you.
> >
> > [ITW-JAVAWS][ERROR_DEBUG][Wed Apr 05 14:57:25 CEST
> > 2017][net.sourceforge.jnlp.Parser.getParserInstance(Parser.java:1351)] NETX
> > Thread# 5fd0d5ae, name main: java.lang.ClassNotFoundException:
> > net/sourceforge/jnlp/MalformedXMLParser
>
> This smell like packaging bug. Missing tagsoup!
If there is any HTML or XML tag I need to add to make it work, I am more than
happy to try.
> >
> > [ITW-JAVAWS][ERROR_DEBUG][Wed Apr 05 14:57:25 CEST
> ...
> >
> > By the way both .jar files are signed.
>
> Are they signed by same cert or each by its own?
Same certificate but they are signed on different dates. Still Kemtrakpro.jar
contains all the important classes, jcalender only contains a calender
implementation.
>
> >
> > [ITW-JAVAWS][MESSAGE_DEBUG][Wed Apr 05 14:57:32 CEST
> > 2017][net.sourceforge.jnlp.tools.JarCertVerifier.
> > getAlreadyTrustPublisher(JarCertVerifier.java:121)] NETX Thread# 4bb62a0b,
> > name Kemtrak 007: App already has trusted publisher: true
> > [ITW-JAVAWS][MESSAGE_DEBUG][Wed Apr 05 14:57:32 CEST
> > 2017][net.sourceforge.jnlp.tools.JarCertVerifier.
> > isFullySigned(JarCertVerifier.java:186)] NETX Thread# 4bb62a0b, name Kemtrak
> > 007: App already has trusted publisher: true
>
> Annyway, it loks very correct, and you should be abel to run *without*
> deployment.security.level=ALLOW_UNSIGNED
I can confirm that I haven't had signing issues running on Oracle Webstart, no
messages about it, no warnings. It should be OK.
>
> >
> > The manifest in the main jar file reads
> > Manifest-Version: 1.0
> > Created-By: 1.6.0 (Sun Microsystems Inc.)
> > Permissions: all-permissions
> > Trusted-Only: true
> > Application-Name: Kemtrak
> > Main-Class: Kemtrak
> > Class-path: jcalendar.jar
> > Codebase: *
> > Application-Library-Allowable-Codebase: *
> >
> >
>
> The manifest file is interesting. Thank you. I will include it in reproducer.
--
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/20170406/fdf0cc6f/attachment-0001.html>
More information about the distro-pkg-dev
mailing list