concept for future magnolia (possibly 3.5)
(MAGNOLIA-587)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.0 Beta 1 |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Sameer Charles |
| 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 |
|
The core API has a lot of dependencies on the servlet API. Since we will use workflow and other kind of interaction (SOAP for example) we introduce a neutral MgnlContext, which give access to the important objects. It holds the current User, Language. It is a subclass of the commons chain WebContext and would therefore be useable for the commands too. Enduser will call MgnlContext.getHierarchyManager(name), MgnlContext.getUser(), MgnlContext.getMessages(). As a side effect magnolia would be able to use JCR implementaions not updating current sessions. |
| Comments |
| Comment by Sameer Charles [ 12/Jan/06 ] |
|
I already commited new MgnlContext and WebContext implementation, although at the moment its a not a subclass of commons.chain.WebContext but ll look in to it. SessionAccessControl will still be available for compatibility with old magnolia versions |
| Comment by Sameer Charles [ 21/Feb/06 ] |
|
create new issue to clean any use of SessionAccessControl |