Integration test is needed to reproduce this issue, I think. Would be small application enough for reproducing the issue on your side?
-----Ursprüngliche Nachricht----- Von: Romain Manni-Bucau [mailto:[email protected]] Gesendet: Sonntag, 21. April 2013 23:10 An: [email protected] Betreff: Re: AW: Java EE Scheduler implementation in TomEE Strict plan no but if you want to work on it (can be a patch or it can start with a unit test showing the issue) we can help/do it Le 21 avr. 2013 22:31, <[email protected]> a écrit : > Just tested with trunk version and JobStoreCMT. There is one limitation: > timers are executed after restart, but method TimerService.getTimers() > returns empty list, making it impossible to remove old timers. Are > there any plans to fix this limitation? > > -----Ursprüngliche Nachricht----- > Von: Romain Manni-Bucau [mailto:[email protected]] > Gesendet: Sonntag, 21. April 2013 16:31 > An: [email protected] > Betreff: Re: Java EE Scheduler implementation in TomEE > > It should be on trunk. There was some limitations but cant remember > which ones. > > Btw it was traced on jira > Le 21 avr. 2013 16:11, <[email protected]> a écrit : > > > That would be great. Is this functionality already implemented in TomEE? > > > > Пользователь Romain Manni-Bucau <[email protected]> писал: > > > > > > Think we can persist stuff through quartz config Le 19 avr. 2013 > > 19:19, <[email protected]> a écrit : > > > > > Hello, > > > > > > I have a question in relation to Scheduling API in TomEE. As I > > > know org.apache.openejb.core.timer.DatabaseTimerStore is not > > > implemented yet, and it means that any task created with > > > TimerService and persistent=true will be not persisted over JVM restarts. > > > Is there any plans or estimations to implement scheduled task > > > persistence in TomEE? > > > We have to use plain Quartz scheduler now as workaround. Will be > > > Quartz API supported in future releases of TomEE? How will it be > updated? > > > > > > Best regards > > > Dmitry Volkov. > > > > > >
