You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2003/04/04 14:50:03 UTC
DO NOT REPLY [Bug 18703] New: -
reading "node DOM" in session attribute not supported
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18703>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18703
reading "node DOM" in session attribute not supported
Summary: reading "node DOM" in session attribute not supported
Product: Cocoon 2
Version: 2.0.4
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
Priority: Other
Component: sitemap components
AssignedTo: cocoon-dev@xml.apache.org
ReportedBy: oliver.charlet@form4.de
the problem occures while the integration of a new xform implementation
(chicoon, see: http://chiba.sourceforge.net).
Basically on a submit in the xform, a connector resolves a cocoon:/... resource
matched to a pipeline, after storing an element node from the xform instance
(which is NOT a document node, but rather an element in the middle of the xform
DOM) in a session attribute.
Now in the pipeline I use a SessionAttributeGenerator to retrieve the DOM(-part)
and process the instance data further before sending back some other XML to the
connector.
When the pipeline consists of only the generator and an XMLSerializer everything
works OK, the XML is send back.
The problem occures, when I add a XSLT Transforner inbetween. The Transformer
throws a NullPointerExcpetion. It seems, that the Transformer does not receive
any SAX Events, or is not able to interprete the input correctly.
While debugging this problem, I tried an ReadDOMSessionTransformer to put the
DOM from the session into a trigger tag.
Here is the resulting XML:
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<root>
<trigger<?xml version="1.0" encoding="UTF-8"?>
><searchresult currentpage="1" xmlns:sql="http://apache.org/cocoon/SQL/2.0">
<baglist label="Page 1" page="1"></baglist>
</suchergebnis>
</trigger>
</root>
</pre>
the error here is the insertion of the XML declaration INSIDE the trigger tag.
the question is, if this is because of the fact that there is not a document
node DOM in the session, but an (life) element node (from inside an document
elsewhere in the same JVM)
question is also, if this is a bug or if the components only accept document
nodes as valid input from the session attribute.
:olli