Bug 20165 - Ability for some actions to be executed in AWT thread
Ability for some actions to be executed in AWT thread
Status: RESOLVED FIXED
Product: platform
Classification: Unclassified
Component: Actions
3.x
All All
: P3 (vote)
: 3.x
Assigned To: David Simonek
issues@platform
: API, THREAD
Depends on:
Blocks: 17597
  Show dependency treegraph
 
Reported: 2002-02-05 14:31 UTC by Jaroslav Tulach
Modified: 2008-12-22 17:42 UTC (History)
3 users (show)

See Also:
Issue Type: TASK
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Tulach 2002-02-05 14:31:56 UTC
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.
Comment 1 Jesse Glick 2002-02-06 11:46:41 UTC
Cf. pnejedly's suggestions re. RequestProcessor API enhancements (or
just better pooling) which may be useful.
Comment 2 Marek Grummich 2002-07-22 11:30:56 UTC
Set target milestone to TBD
Comment 3 Marek Grummich 2002-07-22 11:32:55 UTC
Set target milestone to TBD
Comment 4 Jaroslav Tulach 2003-12-03 10:18:23 UTC
All actions are not in AWT thread unless they explicitly wishes not to be.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo