[Design of JBoss jBPM] - Re: releasing 3.2.Beta1
by tom.baeyens＠jboss.com
summary: high priority for 3.2.Beta1
a) make sure that the user task list only displays tasks for which the current authenticated user is the actorId. (the group task list should display all the tasks for which the current authenticated actor is somewhere in the list of pooled actor ids. also note that the pooled actors could contain the group id to which a user belongs)
The group task stuff is just for your info. In case there would be a problem with it, that doesn't have to be solved in 3.2.Beta1
b) starting the websale process does not navigate to the task form. somehow the web console thinks that the task is unassigned.
David, could you fix these two problems asap and post feedback here ? thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997887#3997887
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997887
19 years, 2 months
[Design of JBoss jBPM] - Re: releasing 3.2.Beta1
by tom.baeyens＠jboss.com
"tom.baeyens(a)jboss.com" wrote : "david.lloyd(a)jboss.com" wrote : - The "new tasks" list is now a list of created tasks, not assigned tasks. This should fix the problem that no tasks are being presented on the screen when a process is started having a start task and no swimlanes or assignment magic.
| |
|
| i would call that list the "Unassigned tasks". it's a good idea. also you could make the initiator responsible for the assignment in case a task is created without an assignment.
|
|
i forgot to mention that this has no real priority as this is navigation and the navigation will probably be shaken pretty significantly when the se's give their feedback.
also i just saw a potential minor problem with this. i just started the websale process. and as the feedback on starting a process instance, i got the 'New Tasks Created' screen with in the table, '(nobody)' in the 'Assigned To' column. When i clicked the task, it appears to be assigned to ernie (the initiator) as to be expected from the process definition. So after starting a new websale process, the user should have been navigated to the task screen instead of the 'New Tasks Created' screen, i think.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997864#3997864
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997864
19 years, 2 months
[Design of JBoss jBPM] - free choice of initial node
by tom.baeyens＠jboss.com
currently, you are forced to have a start-state to mark the initial node in your process-definition.
i think it is a good idea to expand this so that any type of node could be the first node in the process. we already did this with SEAM.
IMO, the most elegant way to achieve this is by adding an optional attribute 'initial' to the process-definition. the value must be a node name. when the initial node is specified as an attribute, the process should not have a start-state.
the result is that with the initial attribute on the process-definition, any node type can be used as the start state.
we would have to update the core engine new ProcessInstance(processDefinition) method. after creating the process instance and positioning the token in the initial node, the initial node has to be executed. now that is not the case. the initial node is not executed.
because the start-state now has an empty implementation, this will be backwards compatible.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997863#3997863
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997863
19 years, 2 months
[Design of JBoss jBPM] - Re: releasing 3.2.Beta1
by tom.baeyens＠jboss.com
"david.lloyd(a)jboss.com" wrote : - The "new tasks" list is now a list of created tasks, not assigned tasks. This should fix the problem that no tasks are being presented on the screen when a process is started having a start task and no swimlanes or assignment magic.
|
i would call that list the "Unassigned tasks". it's a good idea. also you could make the initiator responsible for the assignment in case a task is created without an assignment.
"david.lloyd(a)jboss.com" wrote :
| Also one question I have is this: when a process starts that does not have a task on the start state (and therefore, I presume, no reason to wait), should the token automatically proceed out of the start state? Right now the user must signal the token manually in this case.
wether or not the process should signal automatic with the start should be in the process definition. not in the webapp. currently there is no such feature in which you can specify that the default transition has to be taken automatically when a process instance is created.
for functional behaviour i don't think this is really necessary. you can always add an action on event process-start. then a developer could always turn the start-state into a wait state. but of course, this seriously limits the modeling freedom.
another way to solve this is to do the same as in SEAM page flow. there you can specify an attribute initial="myStartNode" in the process-definition. that way, you are not forced to have a start-state as the initial node in your process definition. i think this would be the most elegant solution.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997859#3997859
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997859
19 years, 2 months
[Design of POJO Server] - Re: ObjectModelFactories parsing empty xml elements
by scott.stark＠jboss.org
There is no reason for the setValue to be called on an empty element. There would have to be both a newChild and setValue to handle both cases. You don't need a separate SecurityDomain as you can return the parent element:
| public Object newChild(ConfigurationMetaData md, UnmarshallingContext navigator,
| String namespaceURI, String localName, Attributes attrs)
| {
| Object child = null;
| if (localName.equals("cluster-config"))
| {
| child = new ClusterConfigMetaData();
| }
| else if(localName.equals("container-interceptors") ||
| localName.equals("container-cache-conf") ||
| localName.equals("container-pool-conf"))
| {
| child = new DomElement(newDomElement(localName, attrs));
| }
| else if(localName.equals("security-domain"))
| {
| child = md;
| // Indicate a security-domain element was seen...
| md.setSecurityDomain(null);
| }
| return child;
| }
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997825#3997825
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997825
19 years, 2 months