> I believe that someone is working on the "sealing viloation" fix that he
> wanted to include in beta 2.
Can someone confirm (from a CVS build) that this bug still exists? The
biggest thing that I need to see from someone else's machine is:
* use the CVS jakarta-servletapi-4,
* use the CVS jakarta-regexp-1.3-dev,
* and make /double-backflippingly/ sure that the jars Catalina uses are still
Sealed: true. The jars in your webapp shouldn't matter, but the ones in the
various lib directories of Catalina must still be sealed (as they are by
default)
In unix, my favorite way of testing this is:
cd $CATALINA_HOME;
for j in `find . -name "*.jar"`; do
echo $j;
unzip -c $j META-INF/MANIFEST.MF | grep Sealed;
done
You should see that jaxp.jar and crimson.jar ARE, repeat, ARE sealed. If
they are not, and you don't get the sealing violation, then you are a victim
of the earlier CVS commits of unsealed jars.
However, if you jump through my little hoops and you still don't (or do)
get the sealing violation, PLEASE send me (and/or the list) email. The
problem has vanished on my development machine, so it makes tracking the
problem a nightmare.
Craig knows all of this, but the more input I can get the better.
-- /v\atthew
--
Matthew L Daniel Never put off until tomorrow what you can do today.
Wizard There might be a law against it by that time.
[EMAIL PROTECTED] -- `/usr/bin/fortune`
