camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Resolved] (CAMEL-6308) ScheduledPollConsumer.startScheduler() access type should be "public", not "protected"
Date Wed, 24 Apr 2013 09:07:17 GMT


Claus Ibsen resolved CAMEL-6308.

    Resolution: Fixed

The startScheduler=false was used internally by Camel itself, and not as much intended for
end users. But since the option is exposed, we should make it easier to use the API from end

Added JMX operations as well.
> ScheduledPollConsumer.startScheduler() access type should be "public", not "protected"
> --------------------------------------------------------------------------------------
>                 Key: CAMEL-6308
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.10.4
>         Environment: any
>            Reporter: Chris Wolf
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.10.5, 2.11.1, 2.12.0
> There are frequent requirements (as I read from the mail list) to be able to alter the
polling behavior of Consumers based on ScheduledPollConsumer, for example when polling should
start and stop. To customize when polling should start, the Endpoint can be configured with
"startScheduler=false", but then how can we programatically start it without using reflection
to override the "protected" access of startScheduler()?  It seems to me that if the option,
"startScheduler=false" is implemented, then the complimentary API, ScheduledPollConsumer.startScheduler()
should be "public". 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message