So as i replied here the memberships are not meant to carry names. Please
continue the discussion at that location.
Regards,
Koen
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3923833#3923833
Reply to the post :
I'm having a problem when assigning a task to a group..
I created a group in the identity component (identity.db.xml), along with the
users and memberships
anonymous wrote : group name=administrationOD
type=administration_generale/
| membership name=administration role=administration
Bonjour Mennen, you had more luck than me. I'm still fighting against these
assignments with the same problems like you. The data of the table
jbpm_id_memberships has all the values ok? Mine (with 3.1B3 and JBoss 403SP1)
returns null in the name field.
Other posts where we try to solucionate
Thanks for your reply boerse
I'm using jbpm 3.0.2, not the beta , with mysql and jboss 4.0.3
I'm still having the problem of membership name still being set to null in the
database. I updated my post
http://www.jboss.com/index.html?module=bbop=viewtopict=76736
Hope this bug is fixed in the
Hi Mennen,
i'm now using 3.1B3 (originally 302) because i wanted to try if 3.1 had this
problem solved, but it hadn't. :(
We're still on it
P.S. Are you sure it's a bug?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3923573#3923573
Reply to the post :
I assumed it's a bug since i am creating the membership in the identity
component like this:
anonymous wrote : membership name=tester role=boss user=mennen
group=myGroup/
And it seems to me that this is how it should be done (according to the
membership.hbm.xml mapping file)
Either that or
So do i...
Anyway i'm going to try 3.1 (final) now... Hope it works, otherwise i'll... :|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3923591#3923591
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3923591
hi yd40, thanks for your answer, have you tried inserting that info via
src/resources/hsqldb/identity.db.xml? does anybody how this could be done so?
i do:
and
then
and in the processdefinition.xml:
and it assigns the task to null :(
Using 3.0.2 w 4.0.3SP1 (not starter kit,
anonymous wrote : I created in the ProcessDefinition a task with this
assignment:
|
| assignment expression='group(group1) -- member(role1)'
|
| where in the DB I have the Identity tables with correct data.
Hi, how did you do that? I mean, create the groups... where did you define
Hi,
I just used the API somthing like this:
IdentitySessionFactory fact = new IdentitySessionFactory();
IdentitySession identitySession = fact.openIdentitySession() ;
identitySession.beginTransaction() ;
User john = new User(john);
User mosh = new User(mosh);
Issak,
I have looked at the issue. You could call it a bug, but there is a reason why
this problem appears. To understand it properly, you should have a look for
yourself in the implementation of the class
org.jbpm.identity.assignment.ExpressionAssignmentHandler. You will see there
that the
Hi Koen,
I looked at the ExpressionAssignmentHandler, and I understood the code.
In my opinion, if you want some users from a group by a spesific role
the actorPooledArray should be set, not the setActorId.
There is no reason to set the first actor from the group or the last actor from
the group,
Well there *is* a reason. If you have e.g. this expression : previous --
group(jbpm-users) -- member(expert) -- group(hierachy) -- member(boss) then
you will have a problem resolving the fourth and fifth expression if there is
more than one expert jbpm-user.
Anyway, providing your own
Ok, so in some cases you need only one actors.
I used the assignment by class that extend the AssignmentHandler,
However I need to pass a String as the role.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3921829#3921829
Reply to the post :
anonymous wrote : When a task is assigned to a group, the actorId property
should be set, rather than the pooledActorArray. The meaning is that the task
is shared by all members of that group, whoever they are. This way new members
can quickly get involved with the responsibilities of the
Hi,
Thank's for the quick response,
I still have to understand something.
let's assume that I have one Group : g1.
In this group I have 4 Users u0 -- u3.
In the memberShip table there is connection between the group and the users:
g1 -- u0-- roleName = role1
g1 -- u1 -- roleName = role1
g1 --
We need to clarify the identity model. In my view, groups are related to
organizational structures. They are less prone to change than the people
enrolled in them. This is why assigning to groups offers more flexibility. When
a task is assigned to a group, the actorId property should be set,
17 matches
Mail list logo
