Bug 117289
| Summary: | HierarchyDenormalization fails to keep track of all the relevant changes | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Web Application Framework | Reporter: | Vadim Nasardinov <vnasardinov> |
| Component: | other | Assignee: | ccm-bugs-list |
| Status: | CLOSED WONTFIX | QA Contact: | Jon Orris <jorris> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | nightly | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-08-03 18:46:42 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Vadim Nasardinov
2004-03-02 16:22:50 UTC
As I pointed out in bullet item 2 of bug 109718, comment #19, one possible way to fix this bug is to make HierarchyDenormalization aware of the "ascendants" of the instance to which HD is attached. This would probably solve both the case of CAT_CATEGORIES.DEFAULT_ANCESTORS described in this ticket and the case of CMS_ITEMS.ANCESTORS described in 109718. The problem with the current implementation of HD is that it only keeps track of the Category (or ContentItem, as the case may be) to which it is attached. It should also be responsible for notifying the ascendants of all the relevant changes made to their ancestor node. For consistency, something similar to change 41195 should also be coded up for cat_categories.default_ancestors and site_nodes.url. Category.java and SiteNode.java should no longer depend on com.arsdigita.util.HierarchyDenormalization. The latter should be deleted. See bug 109718, comment #23. slate |