> Looks like this is not directly a grails problem. I searched all my
> jars for org.xml.sax.Attributes and found it was in xml-apis.jar and
> an xmlrpc-1.2-patched.jar that I need for the xml database (eXist) I
> am using. The xmlrpc-1.2-patched.jar is signed. If I unjar it,
> remove the META-INF directory to remove the signatures and rejar it,
> grails works.
>
> It's unclear why grails was working on Windows and why my app was
> running in Tomcat on Linux without these Security exceptions, but I'm
> glad it is working now, even though what I did may be a "bad thing".
> If anyone can shed some light on this, I'd be grateful.

Hi Jon,

This is an educated guess, but it may be a bug in the Groovy/Grails
RootLoader. I'm not sure what the bug is or what exactly the behaviour
should be though :) I think the "org.xml.sax.*" classes should be
loaded from the JDK *unless* there is a JAR file in "endorsed" that
contains those classes, in which case the classes should be loaded
from that library. It seems, though, that some of the classes are
being loaded from the eXist JAR which I'm fairly sure is wrong.

I'm including the Groovy user mailing list in case someone on there
has any ideas whether this is a class loading bug or not. For
reference, the original thread can be found here:

http://www.nabble.com/can%27t-run-grails-on-linux-due-to-xml-apis.jar-tt18754272.html

Cheers,

Peter

--
Software Engineer
G2One, Inc.
http://www.g2one.com/

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

  http://xircles.codehaus.org/manage_email