You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Omar Al-Safi (Jira)" <ji...@apache.org> on 2019/11/27 10:28:00 UTC
[jira] [Comment Edited] (CAMEL-13807) Component DSL - To configure
components like endpoint DSL
[ https://issues.apache.org/jira/browse/CAMEL-13807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16983352#comment-16983352 ]
Omar Al-Safi edited comment on CAMEL-13807 at 11/27/19 10:27 AM:
-----------------------------------------------------------------
[~davsclaus] I am interested to help on this feature as I think is very cool to see it in Camel 3.1. Probably I'd start working on it in the next coming weeks. Before jumping in, I have some questions:
* As I can see from the {{endpointdsl}}, we let the users access the DSL factory through {{EndpointRouteBuilder}} once they have the endpoint DSL imported. But how do we want to achieve that for the component DSL? I was thinking of adding an additional method for component builder that can give access to the component DSL similar to endpoint builder, something like this
{code}
camelContext.addComponent(new ComponentBuilder() {...});
{code}
Or a second option is that, we can provide the builder in the Component interface, e.g: {{Component.getBuilder().jms().concurrentConsumers(5).keepAlive(6000).build()}}, what do you think which would make sense? Or which approach do you have in mind that better fit?
was (Author: omarsmak):
[~davsclaus] I am interested to help on this feature as I think is very cool to see it in Camel 3.1. Probably I'd start working on it in the next coming weeks. Before jumping in, I have some questions:
* As I can see from the {{endpointdsl}}, we let the users access the DSL factory through {{EndpointRouteBuilder}} once they have the endpoint DSL imported. But how do we want to achieve that for the component DSL? I was thinking of adding an additional method for component builder similar to endpoint builder, something like this
{code}
camelContext.addComponent(new ComponentBuilder() {...});
{code}
Or a second option is that, we can provide the builder in the Component interface, e.g: {{Component.getBuilder().jms().concurrentConsumers(5).keepAlive(6000).build()}}, what do you think which would make sense? Or which approach do you have in mind that better fit?
> Component DSL - To configure components like endpoint DSL
> ---------------------------------------------------------
>
> Key: CAMEL-13807
> URL: https://issues.apache.org/jira/browse/CAMEL-13807
> Project: Camel
> Issue Type: New Feature
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 3.1.0
>
>
> Some components can also be configured, and today you can configure them via
> - spring boot auto configuration
> - camel main configuration
> - java code manually via setter/getter
> - xml syntax via <bean>
> We should look at generating a Java component DSL with fluent builder like camel-endpointdsl. Then its similar and you can configure them
> component().jms().concurrentConsumers(5).keepAlive(6000)
> And then later if/when we do a XML version of endpoint DSL we can do one for components too.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)