Testing with jnlp templating and encountered a problem:

On some client environments we have to work around graphics issue by specifying "-Dsun.java2d.d3d=false" as parameter to the client VM.

Currently the customer could set a switch on the website before launching the app. If the switch is set, we set this parameter in the JNLP file

So in an ideal world our future JNLP template would look like this:

<jnlp codebase="*">
  <information>
    <title>FirstSpirit SiteArchitect (duvel)</title>
    <vendor>e-Spirit AG</vendor>
    <homepage href="http://www.e-spirit.com"/>
    <description>FirstSpirit SiteArchitect (duvel)</description>
    <icon href="img/FSicon.gif"/>
  </information>
  <security>
    <all-permissions/>
  </security>
  <application-desc main-class="de.espirit.firstspirit.client.CMSExplorer">
    <argument>*</argument>
  </application-desc>
  <icon kind="splash" href="img/logo.gif"/>
  <resources>
    <j2se version="1.6+" initial-heap-size="*" max-heap-size="*"/>
    <jar href="fs-client.jar"/>
    <property name="fs.preferIPv6" value="true"/>
    <property name="sun.java2d.d3d" value="*"/>
  </resources>
</jnlp>


The culprit is the 3rd last row: The value "*" here does not match "false" or "true" of the 'real' JNLP and we get a security error.

It would be very bad if the only solution would be a special jar for each combination of values