logo       

RE: FW: Transformation Error: msg#00082

text.xml.saxon.help

Subject: RE: FW: Transformation Error

I don't think this analysis is correct. It's quite possible for a stylesheet to produce an empty result tree (a document node with no children). The issue here is producing a result tree that isn't a well-formed XML document, and then trying to represent this using the DOM.
 
Michael Kay
http://www.saxonica.com/


From: saxon-help-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx [mailto:saxon-help-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx] On Behalf Of Andrew Welch
Sent: 15 June 2005 15:44
To: saxon-help-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
Subject: RE: [saxon] FW: Transformation Error

In the later versions of Saxon you must produce some output otherwise it's an error... I can't remember why but Mike did say.  It is slightly annoying when doing a quick stylesheet to check something out you always have to remember to produce at least some output to avoid this problem.
-----Original Message-----
From: saxon-help-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx [mailto:saxon-help-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx] On Behalf Of Fenlason, Josh
Sent: 15 June 2005 15:34
To: saxon-help-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
Subject: [saxon] FW: Transformation Error

I have a problem in Saxon 8.4.  Transforming with a empty stylesheet gives the error below.  This works in Saxon 6.5.3, but now fails in 8.4.  Also, if I run the test in Java 1.4.2 without Saxon in my classpath, it fails.  Running the test in Java 1.5 without Saxon in my classpath, it completes.  Running in either Java 1.4.2 or 1.5 with Saxon 8.4 in my classpath fails.  Does this look like a bug?  I have attached a simple test to help demonstrate the issue.  Thanks.
,
Josh.
 
 
 
net.sf.saxon.trans.DynamicError: org.apache.crimson.tree.DomEx: HIERARCHY_REQUEST_ERR: This node isn't allowed there.
        at net.sf.saxon.dom.DOMEmitter.characters(DOMEmitter.java:121)
        at net.sf.saxon.event.ProxyReceiver.characters(ProxyReceiver.java:202)
        at net.sf.saxon.event.ComplexContentOutputter.characters(ComplexContentOutputter.java:110)
        at net.sf.saxon.instruct.ApplyTemplates.defaultAction(ApplyTemplates.java:341)
        at net.sf.saxon.instruct.ApplyTemplates.applyTemplates(ApplyTemplates.java:289)
        at net.sf.saxon.instruct.ApplyTemplates.defaultAction(ApplyTemplates.java:331)
        at net.sf.saxon.instruct.ApplyTemplates.applyTemplates(ApplyTemplates.java:289)
        at net.sf.saxon.instruct.ApplyTemplates.defaultAction(ApplyTemplates.java:331)
        at net.sf.saxon.instruct.ApplyTemplates.applyTemplates(ApplyTemplates.java:289)
        at net.sf.saxon.Controller.transformDocument(Controller.java:1367)
        at net.sf.saxon.Controller.transform(Controller.java:1195)
        at SaxonTest.main(SaxonTest.java:43)
Caused by: org.apache.crimson.tree.DomEx: HIERARCHY_REQUEST_ERR: This node isn't allowed there.
        at org.apache.crimson.tree.XmlDocument.checkChildType(XmlDocument.java:616)
        at org.apache.crimson.tree.ParentNode.appendChild(ParentNode.java:341)
        at org.apache.crimson.tree.XmlDocument.appendChild(XmlDocument.java:664)
        at net.sf.saxon.dom.DOMEmitter.characters(DOMEmitter.java:119)
        ... 11 more
<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise