@WolfFisher

Sure, sorry I missed it.

the jBPM designer is only loosely based on UML, just like jBPM itself has some 
things from activitydiagrams but jBPM is definately not 'based''  on it .

There are testcases (in the sourcecode) for the workflowpatterns. It's how we 
(jBPM) look at the patterns of how they can be implemented. So in our opinion 
they are supported. Could be that we implement some more complex node types in 
the future to support them more easily (at least that is what I heard Tom say 
once)

Regarding the role concept, the result of the identity lookup is an actorID. 
That is stored. If you do not use pools or so, it is just an ID. IF you want to 
display the users individual tasks and these group tasks, you have to implement 
it a loop over the id's. It is not in the api. The taskBean could be extended 
however with a method that accepts e.g. a string array and returns a complete 
list of all tasks.

For the communication you need a process instance id , task id or whatever you 
want to signal. If you do not want to use an id directly, you could also build 
something that keeps a mapping from an id generated by you to the jbpm internal 
ID. So you do not pass processes, you pass process references.

If your computer crashes, jBPM leaves of at the point  where the last committed 
transaction took place. If it was the user performing a task, this task will 
still be in hist tasklist. If it was an external system, make sure the 
signalling  part participates in the transaction. e.g.  by using the async 
functionality in 3.1 or jms or (if it ever becomes a widelyaccepted standard, 
WS-Transaction)

Backup and housekeeping functionality (keeping the process database small) is 
currently left to the user

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911028#3911028

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911028


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to