camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Zhemzhitsky (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-3579) Impossible to use multiple quartz schedulers.
Date Sun, 23 Jan 2011 15:30:44 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985345#action_12985345
] 

Sergey Zhemzhitsky commented on CAMEL-3579:
-------------------------------------------

What was the reason to enforce a single scheduler? 
For example in an OSGi environment or any other environment where there are multiple application
I would expect a separate configuration/scheduler per application.
In the current implementation one application can influence other apps by invoking setScheduler(final
Scheduler scheduler). I think it is not an expected behavior. 
Please correct me if I'm wrong.



> Impossible to use multiple quartz schedulers.
> ---------------------------------------------
>
>                 Key: CAMEL-3579
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3579
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-quartz
>    Affects Versions: 2.5.0
>            Reporter: Sergey Zhemzhitsky
>             Fix For: 2.7.0
>
>         Attachments: multiple-schedulers.patch
>
>
> Current implementation of camel-quartz component does not allow to use multiple quartz
schedulers because of static "scheduler" and "JOBS" fields in the QuartzComponent.
> Moreover in the OSGi environment it is not possible to configure a separate scheduler
per bundle.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message