Refactor magnolia Context class hierarchy
(MAGNOLIA-1614)
|
|
| 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: |
|
||||||||
| 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 |