[Bug 3350] Java applet launched via jnlp web-start cannot load. Fails with "Could not initialize applet"

[bugzilla-daemon at icedtea.classpath.org]

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

--- Comment #14 from JiriVanek <jvanek at redhat.com> ---
> > 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

Speaking about mentioning - try to enable java-console (in debugging panel) it
is providing very good info. Yo can separate stdout/err and itw/app logs, and
much more...

> 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.

Nor do I. This is really strange. For me the app works 100% after fixing yours
bug. Also before fixing it worked 100% *except*
deployment.security.level=ALLOW_UNSIGNED -which triggered the bug.

This looks like issue in itw, but I will skip it as (at least for while or
while you bug it again if it harms later) it is different issue.

> > > 
> > > [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.

No. Thats build switch. Looks like your distro (ubuntu) is not using tagsoup
(as it is optional, but crucial ) dependence.
> 
> > > 
> > > [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.

that is good and correct
> 
> > 
> > > 

So your original bug - form code point - seems to be resolved (c#9). 
I will keep this open for a related discussion. But close later.

Now the question is, how much busines blocker it is?


btw - you can (imho) fix this whole thing by using codebase="." in jnlp file.
All troubles should disappear.

-- 
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/397b15b2/attachment.html>