@Alex. If you ordered and everything is processed, wouldn't you be in another state where you have just one transition 'cancel'?
@all Part of the functionality descibed here can already be achieved. I introduced a real state (kind of a milestone) which is explicitly in the model. There is a timer there which checks the value of a certain viariable. If it is not there it repeats this until a certain date/time is reached. One optimization could be that you can attach a kind of listener to a variable that triggers this instead of polling. This makes sure the process is in an explicit state. The transition is taken but waiting for an event to occur. Personally, I've struggled a lot with this, should we create more and more complex nodes or stay at a certain level of simplicity. My gut feeling says the latter is better. But please... prove me wrong ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910286#3910286 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910286 ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
