[ http://issues.apache.org/jira/browse/XALANJ-916?page=all ]

Brian Minchau updated XALANJ-916:
---------------------------------

    Version: 2.4
                 (was: Latest Development Code)

> (Smoketest) ErrorListenerTest throws NPE after building bad stylesheet
> ----------------------------------------------------------------------
>
>          Key: XALANJ-916
>          URL: http://issues.apache.org/jira/browse/XALANJ-916
>      Project: XalanJ2
>         Type: Bug
>   Components: transformation, Xalan-interpretive
>     Versions: 2.4
>  Environment: Operating System: Windows NT/2K
> Platform: PC
>     Reporter: Shane Curcuru
>     Assignee: Xalan Developers Mailing List

>
> TestID: ErrorListenerTest.java r1.5 testCase1(line:232), testCase2(line:319)
> This test has been causing the smoketest to fail in GUMP runs since 
> shortly before Xerces moved to 2.0.1 (note that Xalan CVS still has Xerces 
> 2.0.0, so if you just use CVS it may pass; to reproduce, put xercesImpl.jar 
> 2.0.1 in your java/bin directory).  Hence some behavior change in Xerces 
> between 2.0.0 and 2.0.1 is causing a change in Xalan's error handling 
> behavior.
> It appears that after attempting to build a stylesheet with errors in it 
> using a 
> n ErrorListener that always continues (i.e. it returns even after a fatal 
> error), if after the call to newTransformer() etc. returns you then attempt 
> to 
> access the transformer or continue using it, we throw an NPE.
> Given that this is a clear error condition, the test may not be valid; we 
> should 
> decide if we want to fix Xalan somehow to perform more nicely under error 
> conditions, or make it policy that after an error we may barf and update the 
> test to match.

-- 
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