[ http://issues.apache.org/jira/browse/XALANJ-2134?page=all ]
     
Morris Kwan closed XALANJ-2134:
-------------------------------


> JAXP 1.3: Fix error handling behavior
> -------------------------------------
>
>          Key: XALANJ-2134
>          URL: http://issues.apache.org/jira/browse/XALANJ-2134
>      Project: XalanJ2
>         Type: Bug
>   Components: JAXP
>     Versions: Latest Development Code
>     Reporter: Morris Kwan
>     Assignee: Morris Kwan
>      Fix For: 2.7
>  Attachments: error_handling.patch
>
> Taken from the JAXP 1.3 javadocs on the javax.xml.transform package:
> The ErrorListener on both objects will always be valid and non-null, whether 
> set by the application or a default implementation provided by the processor. 
> The default implementation provided by the processor will report all warnings 
> and errors to System.err and does not throw any Exceptions. Applications are 
> strongly encouraged to register and use ErrorListeners that insure proper 
> behavior for warnings and errors.
> The current ErrorListener implementations in Xalan interpretive and XSLTC do 
> not completely conform to the spec. The default ErrorListener implementation 
> in Xalan interpretive
> throws exceptions on errors and fatal errors. This causes a failure in the 
> JAXP 1.3 TCK (testcase ErrorListener.error001). XSLTC also has its own 
> problems on error handling. For example, it reports a warning by calling the 
> ErrorListener.error() method.
> This is not something new in JAXP 1.3. I believe that JAXP 1.2 also has the 
> same requirement. However, the JAXP 1.3 javadocs make it clearer that the 
> default ErrorListener implementation should not throw exceptions.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to