Bug 115560 - XSLT error in validation in the themes application
XSLT error in validation in the themes application
Status: CLOSED WONTFIX
Product: Red Hat Enterprise CMS
Classification: Retired
Component: APLAWS (Show other bugs)
nightly
All Linux
medium Severity medium
: ---
: ---
Assigned To: ccm-bugs-list
Daniel Berrange
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-02-13 10:44 EST by Arturo Dell
Modified: 2010-09-03 10:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-09-03 10:30:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Arturo Dell 2004-02-13 10:44:56 EST
I’ve been testing the XSLT theme validation, which works, but with 
one small bug

I’ve created intentional errors in the XSLT files but the Error 
Message always points to the file/line number that is importing the 
file with the error in it, rather than the file itself/line.

The nature of the bug itself is reported correctly.

eg.
I mis-spelt <div> as <divse> in:

[theme-name]/types/fileStorageItem.xsl, which is imported by line 15 
of [theme-name]/types/ContentTypes.xsl

Error Messages:

1.http://194.202.210.43:9005/resource/ccm-ldn-theme/__ccm__/themes-
dev/camden-aplaws/types/ContentTypes.xsl:15: 

Message From Original Exception:The element type "divse" must be 
terminated by the matching end-tag "</divse>". 

2.http://194.202.210.43:9005/resource/ccm-ldn-theme/__ccm__/themes-
dev/camden-aplaws/types/ContentTypes.xsl:15: 

Message From Original Exception:The element type "divse" must be 
terminated by the matching end-tag "</divse>".


Similarly I made a bug in /lib/leftNav.xsl which is imported by line 
15 of content-section-index.xsl and got an error pointing to file 
content-section-index.xsl:15 rather than /lib/leftNav.xsl

Note You need to log in before you can comment on or make changes to this bug.