[ http://jira.magnolia.info/browse/MAGNOLIA-1256?page=comments#action_12981 ] Chris Miner commented on MAGNOLIA-1256: ---------------------------------------
The other option is to call save on the new nodes parent. Which in the case of users, groups, and roles is the root node, which means all the nodes in the workspace. At which point I thought both approaches were basically the same and went with the one that would leave the least doubt as to what would happen. > MgnlGroupManager, MgnlRoleManager, MgnlUserManager fail to create groups, > roles, and users respectively via their associated create... methods. > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: MAGNOLIA-1256 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1256 > Project: Magnolia > Issue Type: Bug > Components: core > Affects Versions: 3.0 Final > Reporter: Chris Miner > Assigned To: Grégory Joseph > Fix For: 3.0.1 > > Attachments: patch.txt, stacktrace.txt > > > the group and role managers try to create content rather than groups or > roles. All the classes call the save method on the newly created node, which > fails due to the apparent fact that it isn't allowed to call save on a newly > created node. See attached patch and stack. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
