You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2001/10/09 16:04:42 UTC
DO NOT REPLY [Bug 4044] New: -
SAX Transform after error gives different results than stream
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=4044>.
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=4044
SAX Transform after error gives different results than stream
Summary: SAX Transform after error gives different results than
stream
Product: XalanJ2
Version: 2.0.0
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: org.apache.xalan.transformer
AssignedTo: xalan-dev@xml.apache.org
ReportedBy: curcuru@apache.org
TestID: SmoketestOuttakes.java testCase3 r1.2
TestID: ErrorListenerTest.java testCase2 r1.5
Precis: After attaching an ErrorHandler that ignores all fatalErrors (i.e. does
not re-throw the exception), this test then uses the templates.newTransformer()
created to perform a normal transformation. When done against StreamSource
(URI), the output of the transformation is as expected (i.e. the parts of the
stylesheet unaffected by the error worked as if an error had not occoured).
When done using a SAXTransformerFactory with a SAX InputSource, the
transformation output is incorrect (looks like only the default template rules
were used instead of the stylesheet).
Note: behavior in this case is questionable, but it's unusual that the two
methods produce different results.
Triage: not for 2.2