You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Oliver Strässer (JIRA)" <ji...@apache.org> on 2010/12/03 20:17:11 UTC

[jira] Reopened: (CLEREZZA-369) UserManager Service - store user in contentgraph is missing via service

     [ https://issues.apache.org/jira/browse/CLEREZZA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oliver Strässer reopened CLEREZZA-369:
--------------------------------------


this didn't solve the problem, that no user is generated in the contentgraph.

> UserManager Service - store user in contentgraph is missing via service
> -----------------------------------------------------------------------
>
>                 Key: CLEREZZA-369
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-369
>             Project: Clerezza
>          Issue Type: Improvement
>            Reporter: Oliver Strässer
>            Assignee: Tsuyoshi Ito
>
> I use the UserManager  Service to create a new user from my business logic. After I cretaed the user with userManager.storeUser(userName, email, psw, userRoles, pathPrefix), the user is listed in the usermanager. 
> The problem is, that I can't delete the user in the backend, because the error "User " + userName + "does not exist in our database" is thrown. The reason is: If I create the user via service, the user is created in the system graph.
> If I create the user in the backend, the user ist stored via service and manually in the contentgraph. the method to delete a user, searchs the user in the contentgraph. because the service doesn't add the user in the content.graph, my added user (via service) couldn't be found. 
> summary: 
> I can't delete a user in the usermanager , wich isn't in the content.graph, please extend the usermanager service (storeUser), that the user is added in the content.graph - otherwise its complicated and a developer is wondering, why he can't delete the created user.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.