Jna can be loaded from different jnlp, referenced from my main jnlp (I tried it and it works). Only all jars listed in one jnlp have to be signed by the same certificate. So signed jars would help :-)

Different launching would help, but it is too complicated. I think, that rewriting our code dependant on JNA is far easier than write new JWS.

The licence negotiation is interesting idea... I will suggest it to my bosses :-) Although I don't know, if it is possible with real community projects (with no clear single author).

I wonder, than I haven't found a clear answer, because the problem is general - using LGPL in JWS.

Thanks for all suggestions. Petr

On May 8, 2009 1:47 PM, "Timothy Wall" <twal...@dev.java.net> wrote:

Even if the JNA jars were signed, that wouldn't help you since last I checked Web Start needs all resources to be signed by the same signer.

Web start is just a delivery method, so if you were to provide a separate, locally-launchable download, that would fulfill the "replaceability" requirement, as far as I'm concerned.

You could also negotiate for a different license that meets your company's needs explicitly.