User development, A new message was posted in the thread "Automatic transition from wait state - is it correct?": http://community.jboss.org/message/529267#529267 Author : Maciej Swiderski Profile : http://community.jboss.org/people/swiderski.maciej Message: -------------------------------------------------------------- Hi,   the whole solution was developed to prevent of keeping transaction while waiting for response from external system. The idea is that first step sends request to external system and then goes into the state for a specified period of time (end of transaction). When timer expires the flow is moved to check node to verify if the response is already available. If so, move on to the rest of the process, if not go back to wait state with new timer.   There are no manual creation of timers whatsoever.   I have modified a bit DatabaseIdComposer class to verify if that helps. The solution is rather simple but it works. It records all generated ids as process variable (a map) that keeps count of the executions for given id. If one was already created it appends an index, for instance: first execution       myProcess.1.wait state second execution      myProcess.1.wait state[1]   That solved the problem for my case but I cannot be sure it does not violate anything else and what bothers me is that the process variable is kept for entire life cycle of that process instance.   Cheers, Maciej -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529267#529267