Any JAVA pros out there?

[Double Phister]

I have a JAVA webstart question.

We use devices with a JAVA UI. You connecto to them and about 20MB of JAR files download. This sucks for dial-up. We have an app that can precache the JAR files and uses webstart.

When I compare the precached JAR files to the ones that are on the device I notice that there are prefixes of RT or RM added. What is the reason for this? I'm trying to make a new set of precache files for a device revision that my app doesn't support.

[MikeK]

I did this stuff years ago, but I think I have forgotten more than what I remember. I don't know the actual answer to your question off the top of my head, but I think that the naming of the jar files has something to do with versioning. I think it generates a manifest and whacks it into a jar which comes down with all the rest. Either that or one of the prefixes is for metadata about the jar, and the other one is the actual jar.

Also, if you update the version of one or more of the jar files, the old versions sometimes stay in the cache. I can't remember the naming convention they use for this, but it may have something to do with it.

Also I think from memory that what ends up in the cache is different depending on whether or not your jars are signed. I think it keeps signed jars in a different area to unsigned jars.

These links might be useful:

Web Start docs: link
JNLP spec: link

[Dean]

Originally Posted by R4ND0M_AX3

I have a JAVA webstart question.

We use devices with a JAVA UI. You connecto to them and about 20MB of JAR files download. This sucks for dial-up. We have an app that can precache the JAR files and uses webstart.

When I compare the precached JAR files to the ones that are on the device I notice that there are prefixes of RT or RM added. What is the reason for this? I'm trying to make a new set of precache files for a device revision that my app doesn't support.

20MB downloaded JAR files make baby jebus cry...

[Kevin M]

...what about 20MB .docs?