Currently Execution constrcutor is starting the execution. It means only by creating an execution, the instance is started. I think this could cause problems if we have a new class extending Execution (let say MyExecution).
In MyExecution constructor, we have to call super(...) and then we can set other stuff.
The problem is that MyExecution is executing before all other stuff is done...
Maybe Execution should have another contructor not starting the execution.. Or the current one should test a new paramter... Then we can create a new method (start ?) to start performing operations...
What do you tink ?
Charles
