[MAGNOLIA-1278] MgnlContext.getHierarchyManager(getRepositoryId()).getQueryManager() and MgnlContext.getQueryManager(getRepositoryId()) return unequal values. Created: 18/Dec/06  Updated: 27/Nov/13  Resolved: 19/Feb/08

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Chris Miner Assignee: Sameer Charles
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

I found that:

MgnlContext.getQueryManager(getRepositoryId())

is returning a query manager that can be used for doing queries while:

MgnlContext.getHierarchyManager(getRepositoryId()).getQueryManager()

returns null. Not sure why. My workaround was to use the first call.



 Comments   
Comment by Sameer Charles [ 17/Jan/07 ]

fix on svn

Comment by Chris Miner [ 08/Feb/07 ]

I am still seeing this behavior in magnolia. By the way, what does 'fix on svn' mean in this context where Subversion Commits show nothing, the behavior is still seen, and this report is still classified as Open?

Comment by Magnolia International [ 08/Feb/07 ]

It would mean that some code was commited without a jira reference, and that Sameer left this open because he doesn't feel satisfied with the fix yet ? Did you check the sources ?

Comment by Chris Miner [ 08/Feb/07 ]

ah well that is too bad. would have been good to have been able to have had a look at it. No I didn't check the sources. I used the workaround. My solution would be to drop the method getQueryManager from the hierarchy class. Less code is better.

Comment by Magnolia International [ 19/Feb/08 ]

this was fixed on svn prior to the 3.0.2 release

Generated at Mon Feb 12 03:25:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.