You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org> on 2010/02/08 20:23:28 UTC
[jira] Created: (CLEREZZA-107) Usermanager: method to return user
as resource
Usermanager: method to return user as resource
----------------------------------------------
Key: CLEREZZA-107
URL: https://issues.apache.org/jira/browse/CLEREZZA-107
Project: Clerezza
Issue Type: Improvement
Reporter: Reto Bachmann-Gmür
UserManager.getUserByName(name): deprecate or remove this method, if one has access to the system gaph getting the resource is trivial to get this resource, otherwiese it might be used wrongly as this is done in HierachyManager.
getUserGraphNode(name): it's off little use to have the GraphNode with in "UnionMGraph between a new SimpleMGraph and the system graph". I suggest to have
getUserInSystemGraph(name) : GraphNode -> The user in the system graph
getUserGraphNode(name) : GraphNode -> Returns the current user in an Editable MGraph (i.e. a SimpleGraph but this is implementation specific) with the context of the user node, editing the graphnode('s Mgaph) doesn't cause any change elsewhere.
I'm not sure if we should also include information contained in the content graph, I tend to think taht this should be done elsewhere if needed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CLEREZZA-107) Usermanager: method to return user
as resource
Posted by "Manuel Innerhofer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manuel Innerhofer resolved CLEREZZA-107.
----------------------------------------
Resolution: Fixed
> Usermanager: method to return user as resource
> ----------------------------------------------
>
> Key: CLEREZZA-107
> URL: https://issues.apache.org/jira/browse/CLEREZZA-107
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Manuel Innerhofer
>
> UserManager.getUserByName(name): deprecate or remove this method, if one has access to the system gaph getting the resource is trivial to get this resource, otherwiese it might be used wrongly as this is done in HierachyManager.
> getUserGraphNode(name): it's off little use to have the GraphNode with in "UnionMGraph between a new SimpleMGraph and the system graph". I suggest to have
> getUserInSystemGraph(name) : GraphNode -> The user in the system graph
> getUserGraphNode(name) : GraphNode -> Returns the current user in an Editable MGraph (i.e. a SimpleGraph but this is implementation specific) with the context of the user node, editing the graphnode('s Mgaph) doesn't cause any change elsewhere.
> I'm not sure if we should also include information contained in the content graph, I tend to think taht this should be done elsewhere if needed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CLEREZZA-107) Usermanager: method to return user
as resource
Posted by "Manuel Innerhofer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manuel Innerhofer resolved CLEREZZA-107.
----------------------------------------
Resolution: Fixed
> Usermanager: method to return user as resource
> ----------------------------------------------
>
> Key: CLEREZZA-107
> URL: https://issues.apache.org/jira/browse/CLEREZZA-107
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Manuel Innerhofer
>
> UserManager.getUserByName(name): deprecate or remove this method, if one has access to the system gaph getting the resource is trivial to get this resource, otherwiese it might be used wrongly as this is done in HierachyManager.
> getUserGraphNode(name): it's off little use to have the GraphNode with in "UnionMGraph between a new SimpleMGraph and the system graph". I suggest to have
> getUserInSystemGraph(name) : GraphNode -> The user in the system graph
> getUserGraphNode(name) : GraphNode -> Returns the current user in an Editable MGraph (i.e. a SimpleGraph but this is implementation specific) with the context of the user node, editing the graphnode('s Mgaph) doesn't cause any change elsewhere.
> I'm not sure if we should also include information contained in the content graph, I tend to think taht this should be done elsewhere if needed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (CLEREZZA-107) Usermanager: method to return user
as resource
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Reto Bachmann-Gmür reopened CLEREZZA-107:
-----------------------------------------
> Usermanager: method to return user as resource
> ----------------------------------------------
>
> Key: CLEREZZA-107
> URL: https://issues.apache.org/jira/browse/CLEREZZA-107
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Manuel Innerhofer
>
> UserManager.getUserByName(name): deprecate or remove this method, if one has access to the system gaph getting the resource is trivial to get this resource, otherwiese it might be used wrongly as this is done in HierachyManager.
> getUserGraphNode(name): it's off little use to have the GraphNode with in "UnionMGraph between a new SimpleMGraph and the system graph". I suggest to have
> getUserInSystemGraph(name) : GraphNode -> The user in the system graph
> getUserGraphNode(name) : GraphNode -> Returns the current user in an Editable MGraph (i.e. a SimpleGraph but this is implementation specific) with the context of the user node, editing the graphnode('s Mgaph) doesn't cause any change elsewhere.
> I'm not sure if we should also include information contained in the content graph, I tend to think taht this should be done elsewhere if needed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CLEREZZA-107) Usermanager: method to return user as
resource
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Reto Bachmann-Gmür closed CLEREZZA-107.
---------------------------------------
> Usermanager: method to return user as resource
> ----------------------------------------------
>
> Key: CLEREZZA-107
> URL: https://issues.apache.org/jira/browse/CLEREZZA-107
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Manuel Innerhofer
>
> UserManager.getUserByName(name): deprecate or remove this method, if one has access to the system gaph getting the resource is trivial to get this resource, otherwiese it might be used wrongly as this is done in HierachyManager.
> getUserGraphNode(name): it's off little use to have the GraphNode with in "UnionMGraph between a new SimpleMGraph and the system graph". I suggest to have
> getUserInSystemGraph(name) : GraphNode -> The user in the system graph
> getUserGraphNode(name) : GraphNode -> Returns the current user in an Editable MGraph (i.e. a SimpleGraph but this is implementation specific) with the context of the user node, editing the graphnode('s Mgaph) doesn't cause any change elsewhere.
> I'm not sure if we should also include information contained in the content graph, I tend to think taht this should be done elsewhere if needed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CLEREZZA-107) Usermanager: method to return user
as resource
Posted by "Manuel Innerhofer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manuel Innerhofer resolved CLEREZZA-107.
----------------------------------------
Resolution: Fixed
> Usermanager: method to return user as resource
> ----------------------------------------------
>
> Key: CLEREZZA-107
> URL: https://issues.apache.org/jira/browse/CLEREZZA-107
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Manuel Innerhofer
>
> UserManager.getUserByName(name): deprecate or remove this method, if one has access to the system gaph getting the resource is trivial to get this resource, otherwiese it might be used wrongly as this is done in HierachyManager.
> getUserGraphNode(name): it's off little use to have the GraphNode with in "UnionMGraph between a new SimpleMGraph and the system graph". I suggest to have
> getUserInSystemGraph(name) : GraphNode -> The user in the system graph
> getUserGraphNode(name) : GraphNode -> Returns the current user in an Editable MGraph (i.e. a SimpleGraph but this is implementation specific) with the context of the user node, editing the graphnode('s Mgaph) doesn't cause any change elsewhere.
> I'm not sure if we should also include information contained in the content graph, I tend to think taht this should be done elsewhere if needed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CLEREZZA-107) Usermanager: method to return user
as resource
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833755#action_12833755 ]
Reto Bachmann-Gmür commented on CLEREZZA-107:
---------------------------------------------
reviewing
> Usermanager: method to return user as resource
> ----------------------------------------------
>
> Key: CLEREZZA-107
> URL: https://issues.apache.org/jira/browse/CLEREZZA-107
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Manuel Innerhofer
>
> UserManager.getUserByName(name): deprecate or remove this method, if one has access to the system gaph getting the resource is trivial to get this resource, otherwiese it might be used wrongly as this is done in HierachyManager.
> getUserGraphNode(name): it's off little use to have the GraphNode with in "UnionMGraph between a new SimpleMGraph and the system graph". I suggest to have
> getUserInSystemGraph(name) : GraphNode -> The user in the system graph
> getUserGraphNode(name) : GraphNode -> Returns the current user in an Editable MGraph (i.e. a SimpleGraph but this is implementation specific) with the context of the user node, editing the graphnode('s Mgaph) doesn't cause any change elsewhere.
> I'm not sure if we should also include information contained in the content graph, I tend to think taht this should be done elsewhere if needed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CLEREZZA-107) Usermanager: method to return user
as resource
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834793#action_12834793 ]
Reto Bachmann-Gmür commented on CLEREZZA-107:
---------------------------------------------
getUserInContentGraph uses the deprecated getUSerByName method
> Usermanager: method to return user as resource
> ----------------------------------------------
>
> Key: CLEREZZA-107
> URL: https://issues.apache.org/jira/browse/CLEREZZA-107
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Manuel Innerhofer
>
> UserManager.getUserByName(name): deprecate or remove this method, if one has access to the system gaph getting the resource is trivial to get this resource, otherwiese it might be used wrongly as this is done in HierachyManager.
> getUserGraphNode(name): it's off little use to have the GraphNode with in "UnionMGraph between a new SimpleMGraph and the system graph". I suggest to have
> getUserInSystemGraph(name) : GraphNode -> The user in the system graph
> getUserGraphNode(name) : GraphNode -> Returns the current user in an Editable MGraph (i.e. a SimpleGraph but this is implementation specific) with the context of the user node, editing the graphnode('s Mgaph) doesn't cause any change elsewhere.
> I'm not sure if we should also include information contained in the content graph, I tend to think taht this should be done elsewhere if needed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CLEREZZA-107) Usermanager: method to return user
as resource
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834777#action_12834777 ]
Reto Bachmann-Gmür commented on CLEREZZA-107:
---------------------------------------------
reviewing
> Usermanager: method to return user as resource
> ----------------------------------------------
>
> Key: CLEREZZA-107
> URL: https://issues.apache.org/jira/browse/CLEREZZA-107
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Manuel Innerhofer
>
> UserManager.getUserByName(name): deprecate or remove this method, if one has access to the system gaph getting the resource is trivial to get this resource, otherwiese it might be used wrongly as this is done in HierachyManager.
> getUserGraphNode(name): it's off little use to have the GraphNode with in "UnionMGraph between a new SimpleMGraph and the system graph". I suggest to have
> getUserInSystemGraph(name) : GraphNode -> The user in the system graph
> getUserGraphNode(name) : GraphNode -> Returns the current user in an Editable MGraph (i.e. a SimpleGraph but this is implementation specific) with the context of the user node, editing the graphnode('s Mgaph) doesn't cause any change elsewhere.
> I'm not sure if we should also include information contained in the content graph, I tend to think taht this should be done elsewhere if needed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CLEREZZA-107) Usermanager: method to return user
as resource
Posted by "Manuel Innerhofer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manuel Innerhofer reassigned CLEREZZA-107:
------------------------------------------
Assignee: Manuel Innerhofer
> Usermanager: method to return user as resource
> ----------------------------------------------
>
> Key: CLEREZZA-107
> URL: https://issues.apache.org/jira/browse/CLEREZZA-107
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Manuel Innerhofer
>
> UserManager.getUserByName(name): deprecate or remove this method, if one has access to the system gaph getting the resource is trivial to get this resource, otherwiese it might be used wrongly as this is done in HierachyManager.
> getUserGraphNode(name): it's off little use to have the GraphNode with in "UnionMGraph between a new SimpleMGraph and the system graph". I suggest to have
> getUserInSystemGraph(name) : GraphNode -> The user in the system graph
> getUserGraphNode(name) : GraphNode -> Returns the current user in an Editable MGraph (i.e. a SimpleGraph but this is implementation specific) with the context of the user node, editing the graphnode('s Mgaph) doesn't cause any change elsewhere.
> I'm not sure if we should also include information contained in the content graph, I tend to think taht this should be done elsewhere if needed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (CLEREZZA-107) Usermanager: method to return user
as resource
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Reto Bachmann-Gmür reopened CLEREZZA-107:
-----------------------------------------
merged down ZZ-107 but now there's a permission issue when accessing e.g. the Dashboard
> Usermanager: method to return user as resource
> ----------------------------------------------
>
> Key: CLEREZZA-107
> URL: https://issues.apache.org/jira/browse/CLEREZZA-107
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Manuel Innerhofer
>
> UserManager.getUserByName(name): deprecate or remove this method, if one has access to the system gaph getting the resource is trivial to get this resource, otherwiese it might be used wrongly as this is done in HierachyManager.
> getUserGraphNode(name): it's off little use to have the GraphNode with in "UnionMGraph between a new SimpleMGraph and the system graph". I suggest to have
> getUserInSystemGraph(name) : GraphNode -> The user in the system graph
> getUserGraphNode(name) : GraphNode -> Returns the current user in an Editable MGraph (i.e. a SimpleGraph but this is implementation specific) with the context of the user node, editing the graphnode('s Mgaph) doesn't cause any change elsewhere.
> I'm not sure if we should also include information contained in the content graph, I tend to think taht this should be done elsewhere if needed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CLEREZZA-107) Usermanager: method to return user
as resource
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834795#action_12834795 ]
Reto Bachmann-Gmür commented on CLEREZZA-107:
---------------------------------------------
getUserInSystemGraph usisng a priviledged block to access the system graph, I don't think this should be done here as the result is no of you if the caller has no access to the system graph.
> Usermanager: method to return user as resource
> ----------------------------------------------
>
> Key: CLEREZZA-107
> URL: https://issues.apache.org/jira/browse/CLEREZZA-107
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Manuel Innerhofer
>
> UserManager.getUserByName(name): deprecate or remove this method, if one has access to the system gaph getting the resource is trivial to get this resource, otherwiese it might be used wrongly as this is done in HierachyManager.
> getUserGraphNode(name): it's off little use to have the GraphNode with in "UnionMGraph between a new SimpleMGraph and the system graph". I suggest to have
> getUserInSystemGraph(name) : GraphNode -> The user in the system graph
> getUserGraphNode(name) : GraphNode -> Returns the current user in an Editable MGraph (i.e. a SimpleGraph but this is implementation specific) with the context of the user node, editing the graphnode('s Mgaph) doesn't cause any change elsewhere.
> I'm not sure if we should also include information contained in the content graph, I tend to think taht this should be done elsewhere if needed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CLEREZZA-107) Usermanager: method to return user
as resource
Posted by "Tsuyoshi Ito (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831520#action_12831520 ]
Tsuyoshi Ito commented on CLEREZZA-107:
---------------------------------------
getUserInContentGraph(name): GraphNode
if user not exists in contentgraph => clone user from system.graph (property userName)
> Usermanager: method to return user as resource
> ----------------------------------------------
>
> Key: CLEREZZA-107
> URL: https://issues.apache.org/jira/browse/CLEREZZA-107
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
>
> UserManager.getUserByName(name): deprecate or remove this method, if one has access to the system gaph getting the resource is trivial to get this resource, otherwiese it might be used wrongly as this is done in HierachyManager.
> getUserGraphNode(name): it's off little use to have the GraphNode with in "UnionMGraph between a new SimpleMGraph and the system graph". I suggest to have
> getUserInSystemGraph(name) : GraphNode -> The user in the system graph
> getUserGraphNode(name) : GraphNode -> Returns the current user in an Editable MGraph (i.e. a SimpleGraph but this is implementation specific) with the context of the user node, editing the graphnode('s Mgaph) doesn't cause any change elsewhere.
> I'm not sure if we should also include information contained in the content graph, I tend to think taht this should be done elsewhere if needed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.