-
1. Re: Deploying JB CLient JAR's through Java WebStart - securi
didi1976 Oct 3, 2003 12:47 AM (in response to gurka)Hi!
We have just signed log4j.jar and jbossall-client.jar like our jar-files with our certificate.
Didi -
2. Re: Deploying JB CLient JAR's through Java WebStart - securi
gurka Oct 8, 2003 2:46 PM (in response to gurka)I did the same. The problem ended up being that 3 of the JAR's are actualy signed by Sun, and as such must be in their own JNLP file and included into the main applicaiton JNLP using the tag as follows:
extension name="Sun/JBoss Client Libraries" ref="sun.jnlp" />
The jar's needed in this package are
- jcert.jar
- jnet.jar
- jsse.jar
The remainder of the JBoss/client JARs are unsigned, and I had to end up signing them with our own certificate in order to allow the app to use the "<all-permissions/>" security tag.
So all in all, I ended up with 3 JNLPs:
1 - main jnlp with ref's to my app's JARs plus 2 references to the external JNLPs.
2 - Sun JNLP for the 3 JARs signed by Sun.
3 - JBoss client JARs signed by us. -
3. Re: Deploying JB CLient JAR's through Java WebStart - securi
didi1976 Oct 9, 2003 2:37 AM (in response to gurka)Hi,
you have to split up the jnlp file into several different according to their signing. Below is an example for a Client with JavaHelp and JBoss:
yourclient.jnlp:
<?xml version="1.0" encoding="utf-8"?>
...
<all-permissions/>
<j2se version="1.4+" />
<application-desc main-class="YourClient"/>
jh.jnlp:
<?xml version="1.0" encoding="utf-8"?>
JavaHelp
SUN
SUN JavaHelp
JavaHelp
<!-- -->
<!-- -->
<offline-allowed/>
<all-permissions/>
<j2se version="1.4+"/>
<component-desc/>
jbossclient.jnlp:
<?xml version="1.0" encoding="utf-8"?>
JBoss Client Library
JBoss.org
JBoss Client Library
JBoss Client Library
<all-permissions/>
<j2se version="1.4+"/>
<component-desc/>
Hope that helps,
Didi