Bug 109171 - PatternStylesheetResolver should be the default setting
PatternStylesheetResolver should be the default setting
Product: Red Hat Web Application Framework
Classification: Retired
Component: other (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Vadim Nasardinov
Jon Orris
Depends On:
Blocks: 106597 108156
  Show dependency treegraph
Reported: 2003-11-05 08:54 EST by Daniel Berrange
Modified: 2007-04-18 12:59 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-11-06 18:41:10 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Daniel Berrange 2003-11-05 08:54:54 EST
Description of problem:

The enterprise.init file setting for templating stylesheet resolver
was defaulted to 'PatternStylesheetResolver', however when
c.a.templating.Initializer was removed, the default was reverted to
the LegacyStylesheetResolver. 

The LegacyStyleshsetResolver should not be default since it based on
the deprecated SiteNode & PacakgeType APIs & it severly limited in its
functionality. Since I submitted p4 35159, PatternStylesheetResolver
is fully operational for Core & CMS out of the box.

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Richard Li 2003-11-05 09:16:12 EST
Ah, good ticket. A similar conclusion is being reached on bug 108156.
Comment 2 Vadim Nasardinov 2003-11-06 13:02:13 EST
Addressed with change 37765.

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