Leo,
Just read something that indicates that maybe our quartz.properties is
sometimes found first. So it is probably best to set the
'org.quartz.properties' in the cong/system.properties file to point to
the quartz.properties you want to use.
Andy.
On 21/10/2014 00:57, Andy wrote:
Sure, if
In our shade that's org.apache.openejb.quartz.properties not
org.quartz.properties (don't belive sources but bytecode with
shades;)).
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github:
I've also read somewhere that tomee would be backward compatible again with
the old quartz properties.
If so, won't be a conflict?
[]
Leo
On Tue, Oct 21, 2014 at 7:17 AM, Andy andy...@gmx.de wrote:
Leo,
Just read something that indicates that maybe our quartz.properties is
sometimes found
it is compatible is you configure it manually in application
properties or openejb-jar.xml but that's all.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-10-21 11:34
this is the same quartz as standard one, just packages are different.
So all you can do with quartz can be done out of the box
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
yes, but quartz will be loaded by a different classloader, right?
because when I try
JobDetail jobDetail = newJob(HelloJob.class)
.withIdentity(name+, group1)
.build();
HelloJob will be in the webapp, but quartz will be probably under tomee, so
will
You're concerned that TomEE will not be able to see the HelloJob.class
defined in your app/jar.
This is the job of quartz to ensure that it has your classloader correct
when you add the job. It 'should' be fine, but just write a small test
to convince yourself ;)
Andy.
On 21/10/2014 16:13,
Hi Andy
I did :-(
Grave: MisfireHandler: Error handling misfires: Couldn't store trigger
'group1.1413900600168' for 'group1.1413900600168' job:test.HelloJob
org.apache.openejb.quartz.JobPersistenceException: Couldn't store trigger
'group1.1413900600168' for 'group1.1413900600168'
Hi, did you configure quartz to use TCCL?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-10-21 17:27 GMT+02:00 Leonardo K. Shikida shik...@gmail.com:
Hi Andy
I did
did not know this option...
well, I've added org.apache.openejb.openejb.quartz.use-TCCL=true to
application.properties but made no change.
what does it mean?
[]
Leo
On Tue, Oct 21, 2014 at 1:31 PM, Romain Manni-Bucau
rmannibu...@tomitribe.com wrote:
Hi, did you configure quartz to use
this is a tomee config ignored when you use quartz by itself - same
applies to application.properties. Maybe
org.apache.openejb.quartz.scheduler.threadsInheritContextClassLoaderOfInitializer
as system property or in quartz properties of your shceduler?
Romain Manni-Bucau
Twitter: @rmannibucau
Can you share a simple sample we can run quickly showing it please?
PS (Basic check we didn't ask): did you implement the job with our
shade API or with quartz one?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Hi Romain
after playing a little, it was a silly bug.
I've created another scheduler (in the same tables, but with a different
name) and added the properties using
StdSchedulerFactory factory = new StdSchedulerFactory();
Properties props = new Properties();
Hi
I'd like to create quartz timers not using TimerServiceAPI
Is it possible to be done using the new shaded quartz classes or should I
add another quartz jar to the project?
If I have to add the quartz jar, is it safe?
TIA
Leo
14 matches
Mail list logo
