java.lang.NullPointerException
at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
at com.sun.javaws.Launcher.launch(Unknown Source)
at com.sun.javaws.Main.launchApp(Unknown Source)
at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
at com.sun.javaws.Main$1.run(Unknown Source)
at java.lang.Thread.run(Thread.java:619)

I forgot to say that I have cleared Java cache of installed apps, searched the web with Google for solution, make sure all JARs listed in JNLP are phisically present and accessible... and nothing helps :(

I have found what is causing NPE. Belive it or not, inside my JNLP, I had "&TOKEN=something" in my href attribute of jnlp tag. I was using TOKEN param for my custom security app logins. Obviously, this is reserved word/param of 1.6.xx JWS, because it used to work fine with older versions of JWS/JRE. If I use lowercase: "&token=something", then it works fine.

user504063 wrote:
I have found what is causing NPE. Belive it or not, inside my JNLP, I had "&TOKEN=something" in my href attribute of jnlp tag. I was using TOKEN param for my custom security app logins. Obviously, this is reserved word/param of 1.6.xx JWS, because it used to work fine with older versions of JWS/JRE. If I use lowercase: "&token=something", then it works fine.

... that would be quite a coincidence. Not impossible, but still... Now that you got it working, can you reproduce the error by turning the parameter into TOKEN again?

I don't want to be a douche, but too often I have seen myself fall in the trap of thinking that a specific action fixes a problem while it was something else entirely; the sequence of events simply made it seem so.

gimbal2 wrote:
Now that you got it working, can you reproduce the error by turning the parameter into TOKEN again?

Yes! :)

I suggest you raise a bug report, and see what Oracle has to say about it.

In a perfect world, JaNeLA tool would warn on this,..

In the real world, JaNeLA did at least high-light and prompt you to fix +"..lots of reported problems"+. O_o

JaNeLA is open source, so feel free to improve it.

.. and JWS would warn on this and wouldn't crash with NPE.

JWS is not a debugging tool, but a launch technology for Java rich client apps.

I would vote for an RFE to make the JWS clients reject invalid JNLP files and throw up an error dialog. But I doubt it would be implemented by Oracle & extremely doubt it could be implemented as part of any spec. that anyone else making JREs would pay attention to.