[weld-issues] [JBoss JIRA] Closed: (WELD-92) Unify asynchronous execution interfaces
Pete Muir (JIRA)
jira-events at lists.jboss.org
Mon Nov 2 19:19:06 EST 2009
[ https://jira.jboss.org/jira/browse/WELD-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Muir closed WELD-92.
-------------------------
Resolution: Done
> Unify asynchronous execution interfaces
> ---------------------------------------
>
> Key: WELD-92
> URL: https://jira.jboss.org/jira/browse/WELD-92
> Project: Weld
> Issue Type: Feature Request
> Components: Events, Infrastructure
> Affects Versions: 1.0.0.BETA1
> Reporter: David Allen
> Assignee: Pete Muir
> Priority: Minor
> Fix For: 1.0.0.CR2
>
>
> Since the spec identifies several cases of asynchronous tasks which must be performed, the RI should have a single, consistent set of interfaces to provide the executor services needed and the tasks to be performed. In Java SE 5 and 6, java.util.concurrent does provide useful interfaces for dealing with tasks which are executed by a separate service. It is recommended that the Executor interface be used as-is for those not requiring a timer (just execution in a separate thread of control), and perhaps the Delayed mix-in style interface for tasks requiring a timer or delay of execution. Alternatively, another executor interface can be chosen from SE to provide methods which take both the task to perform and the time delay.
> In general, use of the java.util.concurrent interfaces, and even the implementations where possible, will reduce the amount of code in the RI and make better use of existing Java resources.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the weld-issues
mailing list