Title: Message
|
Could it be that your XSLT is generated textual
output thats not inside a root element?
e.g. this XSLT document would create that
error
<xsl:stylesheet ...>
<xsl:template
match="/">
this is some
text which should be in a root element
If you output the result of your XSLT as text, is
it valid XML?
James
----- Original Message -----
Sent: Monday, June 10, 2002 8:27 PM
Subject: [dom4j-user] Still have that
strange exception
This is using
Dom4j 1.3. Sometimes when I run my app, I get the
following exception:
javax.xml.transform.TransformerConfigurationException:
org.xml.sax.SAXException: Invalid Node in DOM4J content:
[org.dom4j.tree.DefaultText@77b3cd [Text: "[/PERFTEST/atr1]"]]
There is nothing
wrong with my xslt or xml files... the application works fine until I turn the
log level down to where it runs faster... which leads me to suspect threading
isues such as a race condition somewhere. My question for the list is -
how could a race condition in my code cause dom4j to barf like this? I
thought bad pointers and memory corruption were a thing of the past with
Java.
I'm not blaming
dom4j - I'm sure the problem is in my code somewhere - I just wonder if anyone
who has more insight into the dom4j code could lend me a clue as to how this
error could happen? That would give me a better starting place to go
hunting. Thanks!
|
