It can be slightly more complicated than this.
Starting a process instance may result in the creation of multiple tasks assigned to the person starting the task, or it may result in one or more group tasks being created, or some combination therein. If we want to shortcut the single-task case, that's fine, but if there are multiple tasks that are relevant to that user, we should go to an intermediate screen to allow the user to choose the task.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999035#3999035
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999035
"tom.baeyens(a)jboss.com" wrote : ProcessDefinition --> Process
| ProcessInstance and Token --> Execution
|
| Maybe that could already be adopted into the web console for 3.2. But probably that would cause more confusion then it solves, no ?
I like the new terminology a lot better, but I think that changing to "Execution" now would just be confusing. Changing "Process Definition" to "Process" is perfectly reasonable though, in my opinion.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999027#3999027
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999027
"tom.baeyens(a)jboss.com" wrote :
| "bazoo" wrote : I get the following exception when I click "End task" or "More info needed", although the transition does happen: javax.el.PropertyNotFoundException: /main/task/new_tasks.xhtml @41,57 value="#{entry.taskInstance.id}": Property 'taskInstance' is not found on type: java.lang.String
| |
|
| David, are you onto this one ? Can you reproduce ?
|
I could reproduce this, but David already fixed it in cvs.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999015#3999015
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999015
The current form of the web console is definitely not intended as an example to get started with.
This will grow out to become a fully fledged console, too complex for people to start using it as a JSF example.
Of course, we should keep it as easy as possible for developers to tweak it, but including more functionality has priority.
Indeed performance and stress tests are going to be needed. I would leverage the community to do the initial pinpointing of problems and only spend our own resournces on it after a potential SEAM refactoring.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998997#3998997
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998997