Bug 115017 - Not all XSLT transformers use the ErrorListeners to report errors
Summary: Not all XSLT transformers use the ErrorListeners to report errors
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Web Application Framework
Classification: Retired
Component: other
Version: nightly
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Randy Graebner
QA Contact: Jon Orris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-02-05 16:08 UTC by Daniel Berrangé
Modified: 2007-04-18 17:02 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-09-02 17:46:41 UTC
Embargoed:

Attachments (Terms of Use)

Description Daniel Berrangé 2004-02-05 16:08:31 UTC 
Description of problem:
In testing of the Themes application is was discovered that some XSLT
engines do not actually use the ErrorListeners for reporting errors -
merely throwing the exceptions as usual. This means that templates
uploaded to the themes app appear to validate ok, but in fact fail in
use. We can work around this by catching an TransformerException's
thrown and explicitly invoking the fatalError(TransformerException)
method on the supplied listeneer ourselves.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Configure CCM to use JD.XSLT
2. Upload XSL with malformed XML tags 
3. Run theme validation
  
Actual results:
Validation passes, but errors are displayed in the logs.

Expected results:
Validation fails & errors reported through the UI.

Additional info:
Comment 1 Randy Graebner 2004-02-23 14:54:22 UTC 
Changes 40660 and 40659 should fix this problem by checking for the
extra error types.
Comment 2 David Lawrence 2006-07-18 03:06:54 UTC 
QA_READY has been deprecated in favor of ON_QA. Please use ON_QA in the future.
Moving to ON_QA.
Comment 3 Daniel Berrangé 2006-09-02 17:46:41 UTC 
Closing old tickets
Note You need to log in before you can comment on or make changes to this bug.