Re: UnsatisfiedLinkError using Java Webstart with custom classloader
On Mar 17, 9:42 pm, Andi <andreas.schnei...@skillworks.de> wrote:
I have a big problem to get my Application running on java webstart. I
have a custom classloader which will be used for some classes.
JWS *has* been known to be finicky with classloaders,
a lot of apps. used code that could 'discover' the
exact location to which it was downloaded. Changes
between 1.5 and 6.0 made that code break.
I am curious though to know exactly - *why*
are you using a custom classloader?
need to load a dll which will be used by a native interface.
More on that below. *
That works perfect when I have a normal client application but it
doesn't when I use Java Webstart.
Here my jnlp:
<?xml version="1.0" encoding="utf-8"?>
<!-- JNLP File for SwingSet2 Demo Application -->
This is a fib, by the way. This is not
the SwingSet2 application. If we are going
to include comments, it seems sensible to
make them factual. ( And yes, I've been
caught out by the same thing myself ;)
<title>Webstart 6 Bugreport</title>
<jar href="jws6-bugreport-app-1.0.jar" main="true"/>
* OK. I think the nativelib element should be
*after* the jar elements. That is how it is
listed in the JNLP File Syntax here..
JWS has also been known to be very finicky
about JNLP files, though frustratingly, it
makes a poor attempt at parsing invalid files,
and if it reports an error at all, it is usually
pointing to an entirely different element..
So, that brings me to the question..
Have you validated this JNLP file?
You might try validating it against the 1.5 DTD
Does anybody help me with that problem...?
Thanks for every hint
BTW - that was a great example you posted,
I would like to have tried it locally, but
unfortunately I do not have the immediate
means to generate the binary.
And another thing. The JNLP mentions 'bugreport'
in a number of parts. Have you actually lodged
a bug with Sun against this? Have you searched
the Bug DB for other related reports?