Issue With Signed JNLP file

Question

Hello,
There seems to be a restriction in signed JNLP files with regards to relative path set in codebase ?
(when we set the codebase to be a full url of the download site it works.).
The problem for us is we want JNLP file for dev and Prod to be identical and not having to hardcode
download URL.
We have a start.jnlp which start our app. All our jars are signed. To avoid the usual warning message
we decided to sign the JNLP file and include JNLP-INF/APPLICATION.JNLP in our jar that contain the main file.
//start.jnlpl and APPLICATION.JNLP have the following
<?xml version="1.0" encoding="utf-8"?>
<jnlp codebase="webstart" href="start.jnlp">
</jnlp>
Error/Exception
BadFieldException[ The field <jnlp>codebase has an invalid value in the signed launch file: webstart,webstart]
     at com.sun.javaws.jnl.XMLUtils.getAttributeURL(Unknown Source)
     at com.sun.javaws.jnl.XMLFormat.parse(Unknown Source)
     at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
     at com.sun.javaws.LaunchDownload.checkSignedLaunchDescHelper(Unknown Source)
     at com.sun.javaws.LaunchDownload.checkSignedLaunchDesc(Unknown Source)
     at com.sun.javaws.Launcher.prepareLaunchFile(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(Unknown Source)
Any input will be greatly appreciated.
Thanks
Jc

Answer 1

>
There seems to be a restriction in signed JNLP files with regards to relative path set in codebase ?
(when we set the codebase to be a full url of the download site it works.).>That is a problem. Sun seems to think there are many forms of launching where the codebase must be explicitly set for the JNLP to work correctly, and this is one of them. In fact, the only time I know it will work with a relative codebase is when embedding an applet using JNLP - and then it has to have no codebase to work!
>
The problem for us is we want JNLP file for dev and Prod to be identical and not having to hardcode
download URL.>But this is really a matter of approaching the problem the most efficient way, and I would argue that way is to write a build file which will make both versions of the application. It might require a more complicated build file (OK - it will require a more complicated build file), but once it is done you will barely notice any difference in build time, and you can get on with development.