[
https://issues.jboss.org/browse/SEAMCRON-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589496#comment-12589496
]
Peter Royle commented on SEAMCRON-2:
------------------------------------
[09:21am] mojavelinux: john will be happy that I left room for a JMS dispatcher
[09:21am] mojavelinux: he'll likely be interested in helping with the design of
the async support, his hand is johnament
[09:21am] mojavelinux: he's been floating the jms module while jordan has been
busy
[09:27am] Royle: so this feels like a job for interceptors to me. would that be
on the right track?
[09:30am] Royle: I just intercept it, wrap it and background it?
[09:33am] mojavelinux: Royle: yep, that's how it was done in seam 2
http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/src/main/org/jboss/seam/async/
[09:34am] mojavelinux: the key is working out a nice dispatcher interface, then
go ahead and just implement using a thread pool (configured via Seam Config)
[09:34am] mojavelinux: so just some properties that Seam Config can set
[09:34am] Royle: ah k
[09:34am] Royle: cool. so provider configuration boils down to interceptor
config?
[09:34am] mojavelinux: exactly, which interceptor you enable likely
[09:34am] mojavelinux: either that, or the dispatcher is an alternative
[09:35am] mojavelinux: we can play around with it, figure out what works best
> Implement asynchronous method invocation for managed beans
> ----------------------------------------------------------
>
> Key: SEAMCRON-2
> URL: https://issues.jboss.org/browse/SEAMCRON-2
> Project: Seam Cron
> Issue Type: Feature Request
> Reporter: Dan Allen
> Assignee: Peter Royle
> Fix For: 3.0.0.Alpha1
>
>
> 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/org/jboss/seam/async/
> 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
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
