[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-395) Alternate "dispatcher" strategies

Gavin King (JIRA) jira-events at lists.jboss.org
Wed May 30 21:00:08 EDT 2007

     [ http://jira.jboss.com/jira/browse/JBSEAM-395?page=all ]

Gavin King closed JBSEAM-395.

    Resolution: Done

It is now possible to "globally" install a new dispatcher strategy.

The existing implementations are TimerServiceDispatcher and ThreadPoolDispatcher. Someone can write a QuartzDispatcher and JMSDispatcher.

> Alternate "dispatcher" strategies
> ---------------------------------
>                 Key: JBSEAM-395
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-395
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Core
>    Affects Versions: 1.1.0.BETA1
>            Reporter: Gavin King
>         Assigned To: Gavin King
>             Fix For: 1.3.0.ALPHA
> Currently, dispatch of asynchronous calls and events is done via the timer service. There are really good reasons to support other dispatching strategies such as quartz, jBPM, etc. This can be done simply by supporting @Asynchronous(dispatcher="#{name}").

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list