Hey Leif --
I have been through the same exercise recently. I suspect that Sun
decided that problem is in WebStart, but I'm not sure. That was my
take on it, but I didn't realize that an earlier version of jarsigner
actually 'signed' the directory entries. That doesn't make a lot of
sense to me... how do you compute a digest on a directory? Anyway, I
went through all the bugs at WebStart, didn't find a corresponding one,
so I added it. It appears to still be in the internal review phase.
As a short-term fix, I ran some tests with all the non-file entries
stripped out of xml-api.jar's manifest, and as I recall it worked.
That was using merlin, though, not phoenix.
Hardly a satisfactory solution...
Gary
On Tue, 14 Jan 2003, at 12:15 [+0900], Leif Mortenson ([EMAIL PROTECTED]:
> I spent the weekend playing around with getting WebStart working
> using the Phyre application for phoenix. The last hurdle that I came across
> was an a security error while trying to load xml-apis.jar.
>
> It turns out that the error was caused due a bug(?) in jarsigner in 1.4.1_01
> It appears that jarsigner has problems with jars which already have manifest
> entries for directories. This is a reported bug on the sun site:
> http://developer.java.sun.com/developer/bugParade/bugs/4739089.html
> But the problem is that Sun has closed it. I was able to get things working
> by falling back and using the version of jarsigner that comes with 1.3.1_03.
>
> This is my first foray into signing jars so I was wondering if anyone
> with more
> experience might have some advice. It would be nice to be able to the entire
> build using 1.4.1
>
> Thanks,
> Leif
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
