-
1. Re: execution interfaces
csouillard Aug 3, 2007 10:51 AM (in response to tom.baeyens)Good idea to split.
By now this is very hard to use pvm api in a safe way...
We already had problems using some methods in a wrong way...
Sometimes we can write some code working but with side effects
Maybe execute method could use the interface for actions ?
Charles -
2. Re: execution interfaces
mvaldes Aug 3, 2007 11:08 AM (in response to tom.baeyens)I agree as well...
Cast would not be needed all the time, i.e in NodeBeaviour and Action impls. ExecutionController and ExecutionState could replace Execution parameter respectively.
regards,
Miguel Valdes -
3. Re: execution interfaces
tom.baeyens Aug 3, 2007 11:09 AM (in response to tom.baeyens)first iteration is done and committed. please review to see if it makes sense
-
4. Re: execution interfaces
tom.baeyens Aug 6, 2007 5:04 AM (in response to tom.baeyens)renamed ExecutionState to ExecutionAccessor to prevent a name collision with Execution.state property.
The execution state indicates wether an execution is active, ended, cancelled, suspended,... and it also supports user defined states (it's a string property)