[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 #4 from JiriVanek <jvanek at redhat.com> ---
> ITW version 1.6.2-3ubuntu1

Indeed the latest released. I'm wondering about head.
> > 
> > > spec "7.0+" without codebase attribute (Document base).
> > > Earliest allowed version in the jnlp file is 1.7.0.45 and security
> > 
> > That is something better to not to use, but should work fine.
...
> > 
> > In this case jnlp file may be enough.
> 
> I have attached the jnlp file. This is an applet started now by Web Start in
> order to work around the fact that the latest browser no longer allow java
> plugins. This code is on the server of different instruments. The user
> connects to the instrument by typing its IP address in a browser and can
> through the code interact with the instrument. That is why the jnlp file has
> no codebase (according to jnlp spec 7.0+) - the codebase is the document
> base which is different on every instrument.

Hmm..not much more clever from this but ok :)
> 
> > 
> > > However with IcedTea webstart I get
> > > 
> > ..
> > 
> > > java.lang.NullPointerException     at
> > > net.sourceforge.jnlp.security.SecurityDialogs.showMatchingALACAttributePanel(SecurityDialogs.java:405)
> > 
> > 
> > This looks like error in ALACA (application allowable  codebase). This may
> > happen when some mandatory field is missing in jnlp/manifest.  I believe all
> > coarsenesses were fixed in alaca dialogue, so the NPE should not happen -
> > tahts why I'm asking for exact version.
> > The oracle javaws is a bit more benevolent to jnlp specification then ITW
> > is, but thats not an apologise for ITW.
> > 
> > You should be able to workaround this by disabling security manifest checks: 
> > 
> > cat ~/.config/icedtea-web/deployment.properties
> > #Netx deployment configuration
> > #Wed Apr 05 12:51:00 CEST 2017
> > deployment.manifest.attributes.check=NONE
> > 
> > Maybe add also:
> > deployment.security.level=ALLOW_UNSIGNED
> > 
> >
> Thanks for the tip. If I understand correctly these are itweb-settings on

yes
> the client. For this code, different users/computers need to be able to
> connect to the instruments/code remotely so every user would need to change

indeed.

> their settings for the tip to work. Which could be indeed the fix if nothing
> else is possible. It would however be my last resort. Ideally it should run
> on the default settings if possible, so that it would be (in a sense)
> plug-and-play for the user.

Still, may you please verify it helped?
> 
> > 
> > see:
> >  ~/icedtea-web-image/bin/itweb-settings --verbose --help |  grep manifest
> > 
> > maybe it will be enough to set to al but ALAC
> > 
> > Anyway this is not solution for your customers, so, help me to help you.

-- 
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/20170405/ab632948/attachment.html>