Side note: the test was failling before my commit now it is green. About persistence or not you can add properties in a @Configuration method or return an EjbModule instead of an enterprisebean in @Module method; the only constraint is use hsqldb as in memory database. Le 2 sept. 2013 16:15, "tschuler" <[email protected]> a écrit :
> Hi Romain! > > Review result: the test will NOT work because of the @Schedule annotation > - it adds a timer causing the first assert to fail. > Find a similar test for cron (or calendar) timers in the attached java > file. > If you can review it and adapt it to TomEE “standard”, I might add some > more test cases (e.g. for duration timer and date timer). > > I checked again my settings and found out that the behavior (Fired cron > trigger not available) only happens if quartz jobs are persisted to > external database. > Sorry for misleading you. Can you reproduce it now? > > Is it possible to add quartz persistence to tests using the > ApplicationComposer to demonstrate it in an automated test? > > Best regards, > Thomas > > Von: Romain Manni-Bucau [via OpenEJB] [mailto: > [email protected]] > Gesendet: Montag, 2. September 2013 12:07 > An: Thomas Schuler > Betreff: Re: Fired cron trigger not available > > just commited something regarding it, if you want to review the test here > it is: > > http://svn.apache.org/repos/asf/tomee/tomee/trunk/container/openejb-core/src/test/java/org/apache/openejb/timer/GetTimerTest.java > > *Romain Manni-Bucau* > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > *Blog: **http://rmannibucau.wordpress.com/*< > http://rmannibucau.wordpress.com/> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > *Github: https://github.com/rmannibucau* > > > > 2013/9/2 Romain Manni-Bucau <[hidden > email]</user/SendEmail.jtp?type=node&node=4664944&i=0>> > > > Iirc it was using remote ejb right? Can you update it to be a simple > junit > > test (using ApplicationComposer for instance). Then we could include it > in > > tomee unit tests directly. > > Le 2 sept. 2013 11:21, "tschuler" <[hidden > email]</user/SendEmail.jtp?type=node&node=4664944&i=1>> a écrit : > > > > Hi Romain! > >> > >> I already shared the tests for topic "Fired calendar trigger still > >> available" (resulting in > https://issues.apache.org/jira/browse/TOMEE-1011 > >> ). > >> > >> It includes two tests for cron triggers (class TestTimers): > >> - method testCronTriggerNotFiring: Shows that a not fired cron trigger > can > >> be found and canceled. > >> - method testCronTriggerFiring: Shows that an at least once fired cron > >> trigger cannot be found (and therefore cannot be canceled) any more and > >> keeps on firing. > >> > >> Best regards, > >> Thomas > >> > >> > >> > >> -- > >> View this message in context: > >> > http://openejb.979440.n4.nabble.com/Fired-cron-trigger-not-available-tp4664936p4664940.html > >> Sent from the OpenEJB User mailing list archive at Nabble.com. > >> > > > > ________________________________ > If you reply to this email, your message will be added to the discussion > below: > > http://openejb.979440.n4.nabble.com/Fired-cron-trigger-not-available-tp4664936p4664944.html > To unsubscribe from Fired cron trigger not available, click here< > http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4664936&code=dGhvbWFzLnNjaHVsZXJAb3BlbnRleHQuY29tfDQ2NjQ5MzZ8LTE4NTIyNTQ0OTI= > >. > NAML< > http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml > > > > > CheckSchedulerBeanBasicsTest.java (5K) < > http://openejb.979440.n4.nabble.com/attachment/4664946/0/CheckSchedulerBeanBasicsTest.java > > > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Fired-cron-trigger-not-available-tp4664936p4664946.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
