Hi JB,
for now, I do not see other way, for me, than to go forward with my work.
As I am already weeks behind schedule regarding project schedule.
My main requirement ( right now ) is to migrate existing Quartz job classes
( this is about 600-700 classes , and with this my change to Scheduler - I
Hi,
So, I propose two actions:
1. Let me take a look on the PR and see how we can extend the Karaf
Scheduler API, still with Quartz "hidden"
2. I think in your case, you can create your own Scheduler using Quartz.
That would gives you complete control if (1) is not fully convenient for
you. I
Hi JB,
yes, I thought about this - and agree, this change is not all that
favorable for main-stream Karaf implementation.
I did not look at camel-quartz, will look it up - thanks.
One note though - in my "solution" Karaf imports Quartz, not exports, but
either way, I know what you mean.
Hi,
I don't think this approach is the good one.
Quartz is an implementation of the Karaf Scheduler, but we can imagine
other implementations.
That's why the Quartz packages are not directly exported by the Karaf
Scheduler (it's private package). That's really my main concern: Karaf
scheduler
