camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CAMEL-2784) camel-quartz - Each endpoint should create their own scheduler instances so you can start/stop other bundles in osgi without problems
Date Fri, 04 Jun 2010 04:25:51 GMT

     [ https://issues.apache.org/activemq/browse/CAMEL-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen updated CAMEL-2784:
-------------------------------

    Attachment:     (was: camel-quartz-2.4-SNAPSHOT.jar)

> camel-quartz - Each endpoint should create their own scheduler instances so you can start/stop
other bundles in osgi without problems
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2784
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2784
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-quartz
>    Affects Versions: 2.3.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.4.0
>
>         Attachments: camel-quartz-2.4-SNAPSHOT.jar
>
>
> Unfortunately getScheduler on the Quartz API just returns a single shared instance. And
the API does not smell of having a new/create method.
> But to ensure modularity each endpoint should have its own scheduler to ensure no problems
when you start/stop bundles on the fly

-- 
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