"petemuir" wrote : assuming the actor has only one task assigned is a *big* one Of course, and indeed I'm not assuming an actor only has a single task assigned. So, for example, when a human actor logs into some website then indeed a list of tasks will often be very appropriate.
However, when a human actor starts a new process, then I think often a single task will be activated and almost immediately assigned to that very same actor. Likewise, when assigning a specific task of some existing process to the current actor, one in fact knows exactly what task is to be performed. The actor wants to take control of that task, so I think often the actor also wants to start working on the task, and wants to be taken to the task-specific page to get the job done. And above all: I'm not saying that tasks should always be auto-started. But if the application is such that (some) tasks should be auto-started, then I wonder what's the cleanest, most Seam-like way to get it implemented. Thanks, Arjan. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030551#4030551 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030551 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
