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 2009/12/04 17:17:52 UTC

[jira] Created: (CAMEL-2258) Add nice lookup method for processors

Add nice lookup method for processors
-------------------------------------

                 Key: CAMEL-2258
                 URL: https://issues.apache.org/activemq/browse/CAMEL-2258
             Project: Apache Camel
          Issue Type: New Feature
          Components: camel-core
    Affects Versions: 2.1.0
            Reporter: Claus Ibsen
            Priority: Minor


Camel creates the processor at runtime based on the route definitions.

What if you want to adjust a processor at runtime, such as a Throttler, Delayer etc.

What needs is something like
{code}
from(myEndpoint).throttle(200).id("myThrottler").to(myOtherEndpoint);
{code}

And the lookup
{code}
Throttler throttler = context.lookupProcessor("myThrottler", Throttler.class);
throttler.setMaximumRequestsPerPeriod(500);
{code}

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


[jira] Updated: (CAMEL-2258) Add nice lookup method for processors

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-2258:
-------------------------------

    Fix Version/s: 3.0.0

We should consider some API changes in 3.0 which makes Processors having id's using the {{HasId}} marker interface.

> Add nice lookup method for processors
> -------------------------------------
>
>                 Key: CAMEL-2258
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2258
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-core
>    Affects Versions: 2.1.0
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: 3.0.0
>
>
> Camel creates the processor at runtime based on the route definitions.
> What if you want to adjust a processor at runtime, such as a Throttler, Delayer etc.
> What needs is something like
> {code}
> from(myEndpoint).throttle(200).id("myThrottler").to(myOtherEndpoint);
> {code}
> And the lookup
> {code}
> Throttler throttler = context.lookupProcessor("myThrottler", Throttler.class);
> throttler.setMaximumRequestsPerPeriod(500);
> {code}

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


[jira] Commented: (CAMEL-2258) Add nice lookup method for processors

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56264#action_56264 ] 

Claus Ibsen commented on CAMEL-2258:
------------------------------------

Its a little tricky to lookup as Processor dont have ids assigned at runtime, so you gotta find its definition and then traverse the routes to find this definition in the channel to be able to find the processor. Phev

> Add nice lookup method for processors
> -------------------------------------
>
>                 Key: CAMEL-2258
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2258
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-core
>    Affects Versions: 2.1.0
>            Reporter: Claus Ibsen
>            Priority: Minor
>
> Camel creates the processor at runtime based on the route definitions.
> What if you want to adjust a processor at runtime, such as a Throttler, Delayer etc.
> What needs is something like
> {code}
> from(myEndpoint).throttle(200).id("myThrottler").to(myOtherEndpoint);
> {code}
> And the lookup
> {code}
> Throttler throttler = context.lookupProcessor("myThrottler", Throttler.class);
> throttler.setMaximumRequestsPerPeriod(500);
> {code}

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