You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/06/02 18:44:51 UTC
[jira] Created: (CAMEL-2784) camel-quartz - Each endpoint should
create their own scheduler instances so you can start/stop other bundles in
osgi without problems
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
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.
[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
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-2784:
-------------------------------
Attachment: 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.
[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
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CAMEL-2784) camel-quartz - Each endpoint should
create their own scheduler instances so you can start/stop other bundles in
osgi without problems
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59651#action_59651 ]
Claus Ibsen commented on CAMEL-2784:
------------------------------------
Change tactics to let quartz component do as jetty and keep track on the number of jobs and only shutdown when no more jobs
> 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.
[jira] Resolved: (CAMEL-2784) camel-quartz - Each endpoint should
create their own scheduler instances so you can start/stop other bundles in
osgi without problems
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-2784.
--------------------------------
Resolution: Fixed
trunk: 950883.
> 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
>
>
> 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.
[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
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-2784:
-------------------------------
Attachment: 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.
[jira] Commented: (CAMEL-2784) camel-quartz - Each endpoint should
create their own scheduler instances so you can start/stop other bundles in
osgi without problems
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59641#action_59641 ]
Claus Ibsen commented on CAMEL-2784:
------------------------------------
See fuse forum
http://fusesource.com/forums/thread.jspa?threadID=1733&tstart=0
> 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
>
>
> 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.