Need help understanding the local caching of jnlp when creating it via jsp
I'm trying to deploy an app via Web Start. I have occasions when I need to pass arguments, so I'm using JSP to create the JNLP and optionally write arguments.
I need some help in figuring out how to cover my different use cases with as few different jnlps as possible and am confused about the local cacheing logic.
Use 1
Initial install: I pass an init=yes url param which writes a preferences file <argument> to be passed to my app. I don't want this argument cached in my jnlp, as this will overwrite the user's preferences on subsequent launches.
Use 2
Subsequent offline launches: no url params passed.
Use 3
Launch via html link (in a CMS): passes a file=<filename> url param which creates a file <argument> for my app to open. Again, I don't want this argument cached, otherwise launching from, say, the desktop shortcut will reopen this file.
Can anyone explain how best to cover these three use cases?
TIA!
