Refactor magnolia Context class hierarchy (MAGNOLIA-1614)

[MAGNOLIA-1798] don't store HierarchyManager, AccessManager, QueryManager in the request, keep them in the context object itself Created: 25/Oct/07  Updated: 23/Jan/13  Resolved: 01/Nov/07

Status: Closed
Project: Magnolia
Component/s: cache
Affects Version/s: 3.1 M3
Fix Version/s: 3.5 RC1

Type: Sub-task Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-1797 Can't proceed workflow : ClassCastExc... Closed
Template:
Date of First Response:

 Description   

We should not put this objects into the request. When ever one likes to persist the context (attributes) one gets problems (we do that when you start a workflow).

This object are then handled by the RepositoryAcquiringStrategy



 Comments   
Comment by Philipp Bracher [ 26/Oct/07 ]

persisting attributes for wokitems will then be much easier

Comment by ashapochka [ 01/Nov/07 ]

New class AuthRepositoryStrategy stores these objects in the corresponding maps instead of using requests and sessions. WebContextImpl relies on this strategy. SharedAccessManagerStrategy is not implemented yet

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