I guess, I just best only use the form mechanism for now...<br><br><div class="gmail_quote">On Thu, May 28, 2009 at 11:46 PM, Marco Dubbeld <span dir="ltr"><<a href="mailto:marco.dubbeld@gmail.com">marco.dubbeld@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi ,<br><br>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.<br>
<br>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.<br>
<br>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??<br>
<br>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.<br>
<br>Thanks,<br><font color="#888888">Marco<br>
</font></blockquote></div><br>