[
https://issues.apache.org/jira/browse/CAMEL-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020574#comment-13020574
]
Claus Ibsen commented on CAMEL-1669:
------------------------------------
Ben
Unfortunately we haven't been able to find a solution with JAXB to indicate
that an ExpressionNode is optional. So if we do this then as you say, end
users, will have to migrate their Camel routes (if they used XML). The Java DSL
can of course be compatible as its just a matter of keeping existing methods.
We have break'ed in the past, so its not as if, this can only be done in, eg.
Camel 3.0. In fact using an expression would make it more in line with other
EIPs, as its the "Camel way". Using expression offer a much higher degree of
flexibility for end users, as an expression can be virtually anything.
And the throttler EIP isn't the most used EIP, so the change wont affect so
many.
> Throttler - Should be more dynamic and be able to throttle per message
> correlation
> ----------------------------------------------------------------------------------
>
> Key: CAMEL-1669
> URL: https://issues.apache.org/jira/browse/CAMEL-1669
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: Future
>
> Attachments: CAMEL-1669.patch, CAMEL-1669.patch
>
>
> The throttler in Camel is a bit to static. Its only accepts numeric values to
> configure it.
> And it throttle the same for all messages going through it.
> What is needed to let it be more dynamic is:
> - configuration using expression
> - dynamic configuration at runtime, eg passing in new values in a message
> header
> - notion of grouping by using a correlation expression so you can have
> different QoS for different message groups
> ** eg gold, silver and bronze
> See nabble:
> http://camel.465427.n5.nabble.com/Suggestions-on-setting-different-Throttler-values-per-Client-td474883.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
