4:46 p.m.
Hi ,
What is the preferred method of handling tasks in the frontend. a.k.a. based
on what information of the task can the frontend provide the needed user
interaction.
Please do not misinterpret my question, I am fully aware its the
responsibilty of the application and not jbpm to handle the user
interaction, however in jbpm 3 we had controllers and variable mappings, the
possiblity to create your TaskFactory and own task implementations for
example.
So how do we know that one task needs one user interaction and another task
another user interaction? Solely based on the name/id of the task? Or
something similar to jbpm 3, or handle this through assignment/task
startevents??
Sorry, if this information is readily available somewhere, but I tried to
find my answer in the forums, and the wiki and might have missed it. I just
want to make sure what I will do is in line with the new ideas underlying
jbpm4.
Thanks,
Marco
9:58 a.m.
I guess, I just best only use the form mechanism for now...
On Thu, May 28, 2009 at 11:46 PM, Marco Dubbeld <marco.dubbeld(a)gmail.com>wrote:
Hi ,
What is the preferred method of handling tasks in the frontend. a.k.a.
based on what information of the task can the frontend provide the needed
user interaction.
Please do not misinterpret my question, I am fully aware its the
responsibilty of the application and not jbpm to handle the user
interaction, however in jbpm 3 we had controllers and variable mappings, the
possiblity to create your TaskFactory and own task implementations for
example.
So how do we know that one task needs one user interaction and another task
another user interaction? Solely based on the name/id of the task? Or
something similar to jbpm 3, or handle this through assignment/task
startevents??
Sorry, if this information is readily available somewhere, but I tried to
find my answer in the forums, and the wiki and might have missed it. I just
want to make sure what I will do is in line with the new ideas underlying
jbpm4.
Thanks,
Marco
10:09 a.m.
The jpdl schema specifies a complex type called taskType that allows a form
as an attribute. However it does not seem to be used on task in the schema.
The JpdlParser does parse the form element as part of the TaskDefinition.
Does the schema needs an update??
Regards,
Marco
On Fri, May 29, 2009 at 4:58 PM, Marco Dubbeld <marco.dubbeld(a)gmail.com>wrote:
I guess, I just best only use the form mechanism for now...
On Thu, May 28, 2009 at 11:46 PM, Marco Dubbeld <marco.dubbeld(a)gmail.com>wrote:
> Hi ,
>
> What is the preferred method of handling tasks in the frontend. a.k.a.
> based on what information of the task can the frontend provide the needed
> user interaction.
>
> Please do not misinterpret my question, I am fully aware its the
> responsibilty of the application and not jbpm to handle the user
> interaction, however in jbpm 3 we had controllers and variable mappings, the
> possiblity to create your TaskFactory and own task implementations for
> example.
>
> So how do we know that one task needs one user interaction and another
> task another user interaction? Solely based on the name/id of the task? Or
> something similar to jbpm 3, or handle this through assignment/task
> startevents??
>
> Sorry, if this information is readily available somewhere, but I tried to
> find my answer in the forums, and the wiki and might have missed it. I just
> want to make sure what I will do is in line with the new ideas underlying
> jbpm4.
>
> Thanks,
> Marco
>
6154
days inactive
6155
days old
2 comments
1 participants
participants (1)
-
Marco Dubbeld