[
https://issues.apache.org/jira/browse/KARAF-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531086#comment-16531086
]
Toni Menzel commented on KARAF-5483:
------------------------------------
What is the intended solution to this? I learned that since Karaf 4.1.5 we have
KARAF-5558 (Quartz configuration now possible externally).
Now, since karaf scheduler excludes certain packages used by quartz
"org.quartz.impl.jdbcjobstore.JobStoreTX", such as
[https://github.com/apache/karaf/blob/karaf-4.1.5/scheduler/pom.xml#L67] this
will not be supported (intentionally?).
Thats why i came here. What is the best (most practical?) way to approach this
ticket?
1. At first glance, Karaf Cellar might want to provide its own "JobStore" so
that you don't need to rely on the JDBC solution.
2. The other question is why we don't "fix" karaf scheduler imports (optionals)
to make JobStoreTx work. (not sure if it is good anyway).
WDYT?
> Extend Karaf scheduler in cluster mode
> --------------------------------------
>
> Key: KARAF-5483
> URL: https://issues.apache.org/jira/browse/KARAF-5483
> Project: Karaf
> Issue Type: New Feature
> Components: cellar-core, karaf-scheduler
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: cellar-4.1.2
>
>
> Karaf provides a convenient scheduler service. This scheduler is "mono"
> instance. It would be great to extend this with Cellar to have a scheduler
> sync on the cluster (as we have in Quartz scheduler with a shared database
> for instance).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
