From: "David Hooker" <[EMAIL PROTECTED]>
> BTW, the weird exception I see, which I've now also seen on single-cpu
> machines usually looks something like this:
>
> javax.xml.transform.TransformerConfigurationException:
> org.xml.sax.SAXException: Invalid Node in DOM4J content:
> [org.dom4j.tree.DefaultText@b5b80 [Text: "E"]]
>
>
> Sometimes there's different things in the "Text:" part of that exception
> message.
>
> Can someone take a glance in the source and see if this could possibly
> be a thread safety issue or not?

Do you ever get more of a stack trace of what causes the exception? That
might help track it down.

James
-------
http://radio.weblogs.com/0112098/

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com


-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en
_______________________________________________
dom4j-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dom4j-user

Reply via email to