Details
-
Bug
-
Status: Reopened
-
Minor
-
Resolution: Unresolved
-
2.1.11, 2.2
-
None
-
Normal
-
Patch available
Description
Sending document objects from flowscript back to the pipeline using
xmodule:flow-attr produces unexpected results. Also, the examples from
the documentation do not work as described:
http://cocoon.apache.org/2.1/861.daisy.html
The most common error reported is:
'The object type: class java.lang.String could not be serialized to XML"
This issue was discussed recently on the cocoon-users mailing list.
The thread was introduced by Kazo Csaba with the subject "Sending DOM from flowscript to pipeline."
(July 17, 2007)
He has attempted to trace this behavior in the source code and believes that a
possibly-inappropriate conversion to string occurs in some cases.
Jason Johnston suggested moving the issue to JIRA.
I've created a demonstration of this apparent bug and some related problems
in this very brief example:
http://www.csparks.com/xmodulePuzzle.txt
I hope someone can fix or explain the correct usage of xmodule:flow-attr.
Thanks to all,
-Hugh Sparks, hugh@csparks.com
xmodule:flow-attr produces unexpected results. Also, the examples from
the documentation do not work as described:
http://cocoon.apache.org/2.1/861.daisy.html
The most common error reported is:
'The object type: class java.lang.String could not be serialized to XML"
This issue was discussed recently on the cocoon-users mailing list.
The thread was introduced by Kazo Csaba with the subject "Sending DOM from flowscript to pipeline."
(July 17, 2007)
He has attempted to trace this behavior in the source code and believes that a
possibly-inappropriate conversion to string occurs in some cases.
Jason Johnston suggested moving the issue to JIRA.
I've created a demonstration of this apparent bug and some related problems
in this very brief example:
http://www.csparks.com/xmodulePuzzle.txt
I hope someone can fix or explain the correct usage of xmodule:flow-attr.
Thanks to all,
-Hugh Sparks, hugh@csparks.com