Currently it is not guaranteed for actions in which thread they will be executed
- they can be executed in separate thread or in the invoking thread - the first
is more suitable for GUI application the later for scripting ones. But because
of the later, it is necessary to prevent actions from creating its own threads
and invoking itself asynchronously.
On the other hand some actions do need to run in special threads - especially
some need to run in AWT thread. There are rumors about action invocations
jumping from AWT to RequestProcessor thread and back to AWT...
The new action framework focuses on declarative specification of action. It
should also address the AWT need: Allow action to specify that they need to run
in AWT keep them there.
Cf. pnejedly's suggestions re. RequestProcessor API enhancements (or
just better pooling) which may be useful.
Set target milestone to TBD
All actions are not in AWT thread unless they explicitly wishes not to be.