Comments on: Java Web Start’s silly Self Reference http://www.theyellowmarker.org/blog/2007/05/25/java-web-starts-silly-self-reference/ [YAWB] Wed, 23 Jul 2008 22:03:26 +0000 hourly 1 By: Ulon http://www.theyellowmarker.org/blog/2007/05/25/java-web-starts-silly-self-reference/comment-page-1/#comment-562 Ulon Fri, 06 Jul 2007 09:45:36 +0000 http://www.theyellowmarker.org/blog/2007/05/25/java-web-starts-silly-self-reference/#comment-562 mmm i give up! don't know the metatag to show code :-( mmm i give up! don’t know the metatag to show code :-(

]]> By: Ulon http://www.theyellowmarker.org/blog/2007/05/25/java-web-starts-silly-self-reference/comment-page-1/#comment-561 Ulon Fri, 06 Jul 2007 09:44:46 +0000 http://www.theyellowmarker.org/blog/2007/05/25/java-web-starts-silly-self-reference/#comment-561 sorry, code was not visible, lets try this: sorry, code was not visible, lets try this:

]]> By: Ulon http://www.theyellowmarker.org/blog/2007/05/25/java-web-starts-silly-self-reference/comment-page-1/#comment-560 Ulon Fri, 06 Jul 2007 09:43:32 +0000 http://www.theyellowmarker.org/blog/2007/05/25/java-web-starts-silly-self-reference/#comment-560 Well, in fact the URL is important. JNLP files can be saved locally, it's even possible to create shotcuts in the user desktop. Consider the next JNLP code: When executed, it will create a shortcut in your desk and force an online check every time the user runs the application (this is useful when you want to update in a transparent fashion). Without the URL, the JNLP will be unable to find the source of the JAR's and therefore the execution will fail. Bear in mind that the JNLP file is supposed to be located in the client machine. The browser downloads it and then runs it. It isn't run in the server side. But i suppose that if you don't need to create shorcuts it will work. Does it work if you add like other jars, etc.?? Gruss, Ulon. Well, in fact the URL is important.

JNLP files can be saved locally, it’s even possible to create shotcuts in the user desktop.

Consider the next JNLP code:

When executed, it will create a shortcut in your desk and force an online check every time the user runs the application (this is useful when you want to update in a transparent fashion).

Without the URL, the JNLP will be unable to find the source of the JAR’s and therefore the execution will fail.

Bear in mind that the JNLP file is supposed to be located in the client machine. The browser downloads it and then runs it. It isn’t run in the server side.

But i suppose that if you don’t need to create shorcuts it will work.
Does it work if you add like other jars, etc.??

Gruss,
Ulon.

]]>