startStateMachine does not provide unique instance names when multiple contexts are given
GoogleCodeExporter opened this issue · 1 comments
GoogleCodeExporter commented
*Needs to be verified with a unit test*
When startStateMachine() is called with multiple contexts, the machines that
are started must get unique instance names. Needs to also consider if a
taskName is provided to startStateMachine.
Original issue reported on code.google.com by jcoll...@vendasta.com on 6 Nov 2012 at 8:30
GoogleCodeExporter commented
Added a unit test to test this. It appears to be working correctly.
Original comment by jcoll...@vendasta.com on 6 Nov 2012 at 9:47
- Changed state: Invalid