When my Application.jar is being started with Java Web Start, it can't load the jogl native binding (jogl.dll in the case of Windows, for example). Web Start says:

1

nojoglinjava.library.path

However, if the same Application.jar ist put next to the jogl.dll on a local filesystem, a double click on Application.jar works fine as expected. (Because the java.library.path contains "." on Windows I suppose).

Of course my .jnlp file contains a native resource elements containing the jogl bins for the various platforms. When I look into the Java Web Start cache folder I see the jogl-native-xyz.jar which has been decompressed to another folder (containing the jogl.dll then).

What with my game having similar problems, i'm wondering if i'm using the resource tag correctly. I keep seeing different strings used (such as os="Mac OS X" or os="MacOS"). Is there a list of 'proper' OS strings to load native libraries with?

Check the JNLP of the webstart demos on the JOGL project page. They work for me.

As for names like "Mac OS X" these strings must match what the system property "os.name" returns... For Mac OS X this is the string "Mac OS X".. I think you only have to match as many characters as you provide.. e.g. .startsWith(blah). so for all versions of windows you can say "Windows" and it will match "Windows 2000" "Windows XP", etc.

Ok, thanks again. There are some pitfalls with Web Start...I've changed the OS strings. The jogl.dll does also work now. No idea why it didn't before, but well, it's OK now.Like Kev said: "however, the MacOS tag does work, although from the explanation above... I don't know why". Looks like we all don't know what Web start does exactly. ;-)

Still, with some browsers (Opera) it's possible to click the .jnlp file on my site and everything works. On another PC with another browser (Mozilla I think) and another JRE the .jnlp file is being started but then Web Start stops with errors ("invalid Xml tags" or such).

Is there anything I can do so that it always works? Creating a Java Script? ... :-(

Hi Kev, thanks a lot. On the vampHQ I didn't find the MIME problem being explained (bit a lot of other things), however PHP thing of your nice and short Howto does do the trick.I've added the two lines and renamed the .jnlp to .php and it looks like it works (for me and another PC, too). That would be cool. Have to test further but hey presto. Presto? Preston.

Say you would like to use this yet unofficial sun.misc.Perf high-res timer (an equivalent one with another name will be there in J2SE 1.5), which is hidden in the J2SE 1.4.2 . Would the following line in the .jnlp do the trick?

I don't think that will work. I thought the '+' ('this version and newer') could only be used with one dot, like 1.3+ or 1.4+ .. but not 1.3.0+You can use '*' so anything beginning with 1.4.2 is 1.4.2* .. which won't match 1.5, but you could have a separate section in the JNLP that had 1.5+

I think the idea is that your code should generally require only a particular major release, but not be so picky about maintenance releases. If it is that picky then you can specify the exact release. I don't think the mechanism was intended to pick out unsupported details in the sun.* packages, since a release with the same version # does not need to implement unsupported sun.* code.

E.g. the mac version of 1.4.2 may have problems if the hi-res timer is not there, but you see version 1.4.2 and assume it is. It would be better to check if is there by catching the exception if it is missing and fall back to a supported option. (not for every call to use the timer... just once to decide which implementation to assign to your timer interface.)

Such happens to me all the time because of that "view 10 recent postings" limit...:)

The Xith tutorial on Webstart is nice, thank you. I've already applied Kev's PHP trick to my Jnlp file. For some friends this worked then. However there are still some who say it doesn't work. Somehow even the .php Webstart file isn't regonized by their browser and they obtain an corrupted .jnlp file with corrupted newlines and so their native Webstart complains about missing tags, etc.Is there something I can do against this? I've to add I'm on one of those free web space providers (they suck, usually, I know)... Would a small example with URL help?

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org