users@jaxb.java.net

progress + problems with using JAXB over webstart

From: <Andrew.Ferguson_at_arm.com>
Date: Mon, 26 Jan 2004 11:08:49 +0000

hi,

 I've separated the jaxb jars into a separate jnlp file which is included
as an extension. The problem is that the application won't start because it
thinks some resources aren't signed. Through a process of elimination it
seems to be something in the jaxb jars. I've tried verifying all of them
and all work except relaxNGDatatype.jar which says:

      H:\public_html\testapp\lib>jarsigner -verify relaxngDatatype.jar
      jarsigner: java.lang.IllegalStateException: zip file closed

I've tried this against various versions of the relaxngDatatype.jar (e.g.
with the jwsdp1.3 version and the latest binary JAXB drop version, and one
from the maven repository from Jan) and all say the same thing. I've worked
around this by unpacking and rezipping, and resigning the jar and including
it as part of my jnlp file rather than as part of jaxbs.

It'd be really useful if anyone could see if relaxNGDatatype.jar causes
similar problems for them with jarsigner.

thanks,
Andrew


>Hi Ed,
>
> thanks for the reply :)
>
>I've signed my own generated jars and added them all in the same JNLP as
>the original jwsdp 1.3 jars but WebStart complains that
>
> JAR resources in JNLP file are not signed by same certificate
>
>I thought it might be possible to multiple people to sign jars but by the
>sound of it this isn't the case?
>
>any help appreciated,
>thanks,
>Andrew




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: users-help_at_jaxb.dev.java.net