[
https://issues.jboss.org/browse/JBESB-3708?page=com.atlassian.jira.plugin...
]
Tom Cunningham reopened JBESB-3708:
-----------------------------------
Reopening to deal with error in chain when a DOM is processed twice :
SystemId Unknown; Line #0; Column #0; org.w3c.dom.DOMException:
HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it
is not permitted.
XsltAction cannot handle org.w3c.dom.Document
---------------------------------------------
Key: JBESB-3708
URL:
https://issues.jboss.org/browse/JBESB-3708
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.10
Reporter: David Tucker
Assignee: Tom Cunningham
Fix For: 4.11
Currently the XsltAction can handle the following objects:
String, byte[], Reader, InputStream, File, or Source
The output from the XsltAction, when choosing DOM, is an object that implements the
interface org.w3c.dom.Document. The action can't accept the document it created to run
another transformation on it. While this scenario is remote at best, it is not unlikely
that we would want to run a transformation on a Document. I was able to create a custom
action that would allow me to put a Document into a DOMSource object. This requires extra
work anytime I want to use a Document in an XSLT and the Document interface should be an
accepted way of sending a document to be transformed. The following code was all it took
in my custom action:
DOMSource domSource = new DOMSource();
domSource.setNode(doc.getFirstChild()); //doc is an object implementing
org.w3c.dom.Document
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira