Red Hat Bugzilla – Bug 779178
XsltAction - non-well formed XML message is silently transformed to empty string
Last modified: 2010-01-05 03:49:33 EST
Date of First Response: 2009-12-02 05:41:06
I ma not sure what should be correct behavior of this test case. If I send the non-wellformed message to XxsltAction then there is a message written into log
09:18:49,541 ERROR [STDERR] SystemId Unknown; Line #2; Column #10; The end-tag for element type "catalog" must end with a '>' delimiter.
and the pipeline processing continues with empty String.
I am not sure that this is a correct behavior.
Jirka, can you provide an example please
Run ant valid to see valid transformation
Run ant invalid to see the transformation of non-wellformed XML file
Log contains message
09:35:03,711 ERROR [STDERR] SystemId Unknown; Line #2; Column #10; The end-tag for element type "catalog" must end with a '>' delimiter.
But no exception is throws and processing is finished with empty string as output of transformation
Attachment: Added: xslt.zip
Link: Added: This issue depends JBESB-3036
Please re-test now that JBESB-3036 has been closed according to process. Thank you.
Verified in ER6