[
https://jira.jboss.org/jira/browse/JBPM-1878?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-1878:
----------------------------------------
Historically jBPM has been kind of 'ignorant' with regard to this. If the endusers
wanted to interpret it as group, they could (although not really handy). The console
should interpret it as a principal assignment (although the java principal is also kind of
undecisive in this area iirc, it could be a group as well).
Deny principal names that already act as group names
----------------------------------------------------
Key: JBPM-1878
URL:
https://jira.jboss.org/jira/browse/JBPM-1878
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: GWT Console 1.0.0 Beta1
Reporter: Heiko Braun
Assignee: Heiko Braun
Fix For: GWT Console 1.0.0 CR1
It leads to unclear assignments. I.e. in the sample database exists a group
'user' and a principal 'user'.
If you assign a task (setActorId) to 'user', what should it be? A group or a
principal assignment?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira