Leif:
Gary Shea has (Avalon Users List) has been hitting the same problem (unsigned manifest entiries). I've been doing some reactive changes in Merlin to handle scanning of jar files using some alternative strategies to manifest lookup - but its still playing around time. The objective is to get to manifest independent loading strategy without sacrificing performance though unnecary scanning - and also - to enable scanning indpendely of the need to lauch an XML parser. OK - this is probably no immediate help - but its a hint at what happening around the issue.
Cheers, Steve.
Leif Mortenson wrote:
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]>
-- Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
