[seam-issues] [JBoss JIRA] Updated: (SEAMCRON-2) Implement asynchronous method invocation for managed beans

[ https://issues.jboss.org/browse/SEAMCRON-2?page=com.atlassian.jira.plugin... ] Peter Royle updated SEAMCRON-2: ------------------------------- Description: Implement thread pool-based asynchronous method invocation for managed (non-EJB) beans. This feature allows developers to mark a method for background execution using an annotation. {code:java} public class BeanWithAsyncMethod { @Asynchronous public void doLongOperation() { ... } } {code} We may consider offering the task control (Future) that EJB 3.1 provides, though you can create that as a separate issue if you deem it follow-up work. See: http://download.oracle.com/javaee/6/tutorial/doc/gkkqg.html was: Implement thread pool-based asynchronous method invocation for managed (non-EJB) beans. This feature allows developers to mark a method for background execution using an annotation. {code:java} public class BeanWithAsyncMethod { @Asynchronous public void doLongOperation() { ... } } {code} To be forward thinking, we should put the @Asynchronous annotation (and related) and the dispatcher interface in Solder so that we can have different providers. For instance, Seam JMS could alternatively be used to execute the method over JMS to provide guaranteed execution instead of Seam Cron's default thread pool approach. You can use similar functionality from Seam 2 as a reference: http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/src/main/... We may consider offering the task control (Future) that EJB 3.1 provides, though you can create that as a separate issue if you deem it follow-up work. See: http://download.oracle.com/javaee/6/tutorial/doc/gkkqg.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira