hmmm... then I don't understand your problem correctly (I think) Let me summarize: - one task per tasknode and a fork advantage: you can have a generic page which shows only the transitions for that task(node). disadvantage: write code to cancel other task
- two tasks per tasknode and no fork advantage: other task is cancelled if one of them is acted upon (no code) disadvantage: create custom page per task I'd go for the latter and imo there is more than a little difference. A custom page will be very easy with jBPM 3.2 (one copy action and one delete (of one of the transition buttons) You could even make one page with a dynamically visual buttons for taking the transitions. Cavalera: the node leave is to late in the handling of the action. One is already selected then, so all you can do is throw an 'not-allowed' exception e.g. and handle that in the page. Not an elegant solution. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3939660#3939660 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3939660 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
