Oxygen XML Forum

I was able to follow the JWS install setup directions (http://www.oxygenxml.com/doc/ug-editor/ ... aller.html), and with a few tweaks, I was able to get it to work with maven. As part of my install, I created a second oxygen.jnlp file (oxygenBeta.jnlp).

oxygen.jnlp's jnlp codebase attribute points to serverA:

<jnlp codebase="http://serverA.com/oxygen/1.0-SNAPSHOT/ ... /oxygenJWS" href="oxygen.jnlp">

while oxygenBeta.jnlp codebase attribute points to serverB:

<jnlp codebase="http://serverB.com/oxygen/1.0-SNAPSHOT/ ... /oxygenJWS" href="oxygenBeta.jnlp">

However oxygenBeta.jnlp will not work because the JWS setup process only signs oxygen.jnlp. It would be nice if there was a packager.properties property that allowed you to indicate all the .jnlp files that needs to be signed as part of the packaging process.

In this way, you only have to run through the JWS set process once, and then put the install files on different servers and just point your index.html to the respective .jnlp file.

Hi,

Signing the JNLP file actually means that a copy of it will also be included in the deployer.jar JAR library under the folder path:
JNLP-INF/APPLICATION.JNLP

This is done in the Oxygen JWS build.xml using the target:
But only one JNLP file can be signed this way because the file name in the JAR file is unique: APPLICATION.JNLP.

So using this approach you can sign only one JNLP file.

But there seems to be an interesting approach described here:

http://blogs.oracle.com/thejavatutorial ... les_with_a

which seems to say that you you copy to the JAR library in JNLP-INF/APPLICATION_TEMPLATE.JNLP a JNLP content which contains * instead of a specific @href attribute value, then both JNLP files used to start the JWS deployment would be considered signed by the Java Runtime. But this has to be tested.

Regards,
Radu