1. Scope
a) All timers in the same EJB module
2. Runtime:
b) Timers from 1a or 1b running on any instance in the cluster
3. Cancelation:
b) Only the bean that owns a timer can cancel it.
The a) in Cancelation seems difficult to implement (no really an issue) but
also dangerous.
If the application wants to do that, it should be possible using CDI events.
Jean-Louis
Le 19 avril 2012 07:36, Pete Muir <pmuir_at_bleepbleep.org.uk> a écrit :
> +1
>
> On 19 Apr 2012, at 07:54, Reza Rahman wrote:
>
> > This is very useful. Responses below:
> >
> > 1. Scope
> > a) All timers in the same EJB module
> >
> > 2. Runtime:
> > b) Timers from 1a running on any instance in the cluster
> >
> > 3. Cancelation:
> > a) Timers returned by this method can be canceled by the caller (i.e.
> > even if it doesn't own the timer)
> >
> > -----Original Message-----
> > From: Marina Vatkina [mailto:marina.vatkina_at_oracle.com]
> > Sent: Wednesday, April 18, 2012 5:01 PM
> > To: jsr345-experts_at_ejb-spec.java.net
> > Subject: [ejb-spec users] [jsr345-experts] TimerService.getAllTimers()
> > (EJB_SPEC-47)
> >
> > Experts,
> >
> > Do you think it is useful to add a method to the TimerService -
> > getAllTimers() - (see http://java.net/jira/browse/EJB_SPEC-47) that will
> > allow to get a collection of all active timers in this application?
> >
> > If you think it is useful, which options should be supported:
> >
> > 1. Scope
> > a) All timers in the same EJB module
> > b) All timers in the same application (EAR file)
> >
> > 2. Runtime:
> > a) Timers from 1a or 1b running on the same server instance
> > b) Timers from 1a or 1b running on any instance in the cluster
> >
> > 3. Cancelation:
> > a) Timers returned by this method can be canceled by the caller (i.e.
> > even if it doesn't own the timer)
> > b) Only the bean that owns a timer can cancel it.
> >
> > If you think there is no need for the new API, please say so.
> >
> > Best,
> > -marina
> >
> >
> >
>
>