[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-4399) Specify the Quartz job name for @Asynchronous methods
Nikolay Elenkov (JIRA)
jira-events at lists.jboss.org
Wed Sep 2 02:41:23 EDT 2009
[ https://jira.jboss.org/jira/browse/JBSEAM-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nikolay Elenkov updated JBSEAM-4399:
------------------------------------
Attachment: quartz-full-job-name.patch
support Quartz 'full name' format: "group.name".
> Specify the Quartz job name for @Asynchronous methods
> -----------------------------------------------------
>
> Key: JBSEAM-4399
> URL: https://jira.jboss.org/jira/browse/JBSEAM-4399
> Project: Seam
> Issue Type: Feature Request
> Affects Versions: 2.2.0.GA
> Environment: JBoss 4.2.x, JBoss 5.x, Quartz
> Reporter: Nikolay Elenkov
> Attachments: quartz-full-job-name.patch, quartz-job-name.patch
>
>
> When using the Quartz dispatcher, Seam implements asynchronous methods by creating Quartz job and trigger
> for every method, annotated with @Asynchronous. The QuartzDispatcher class uses UIDs for the job and trigger names,
> in order to generate unique names. While this is OK for one-off jobs and asynchronous events, it is not suitable for
> repeatable and cron jobs that might have to be paused, cancelled or rescheduled by the application. Jobs should
> have meaningful names, especially when they are saved in a database store.
> Requesting a means to specify the Quartz job name when declaring an asynchronous method. One way to do
> this is to add a new parameter annotation, JobName. The Quartz dispatcher should inspect the asynchronous
> method parameters and use the one annotated with @JobName (if any) as the base for the job/trigger name.
>
--
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 seam-issues
mailing list