[MAGNOLIA-323] Make AccessManager accessible or create methods to create Content with custom nodetype Created: 23/Mar/05  Updated: 23/Mar/05  Resolved: 23/Mar/05

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

Type: Task Priority: Minor
Reporter: Thomas Bach Assignee: Sameer Charles
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

All


Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

snippet from the userlist:
--------------------------

hmm yes its missing, ll add this to current svn trunk.

> There are constructor methods from the Content-Class that allow us to use our custom nodetypes, but the last argument
> of this method is an AccessManager.
> We found no way to retrieve the AccessManager from anywhere. So, we added an accessor to the ContentHandler-Class.

AccessManager is created once you log in and yes its only accessible from the session. AccessManager is only used if you retrieve hierarchy manager
from SessionAccessControl otherwise its ignored.
ll add missing methods to Content class where it belongs.

could you please add this to JIRA?
http://jira.magnolia.info

thanks

  • Sameer


 Comments   
Comment by Sameer Charles [ 23/Mar/05 ]

on svn
http://svn.magnolia.info/svn/magnolia/trunk/src/main/info/magnolia/cms/core/Content.java
http://svn.magnolia.info/svn/magnolia/trunk/src/main/info/magnolia/cms/core/ContentNode.java
http://svn.magnolia.info/svn/magnolia/trunk/src/main/info/magnolia/cms/core/HierarchyManager.java

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