[jira] [Commented] (CAMEL-15049) camel-endpointdsl - Specify component (bean) name without using uri

["Claus Ibsen (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-15049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105365#comment-17105365 ] 

Claus Ibsen commented on CAMEL-15049:
-------------------------------------

Just wonder what a good method name would be?

I have this little unit test
{code}
                SedaComponent seda2 = new SedaComponent();
                context.addComponent("seda2", seda2);

                from(seda("foo")).to(mock("result"));
                from(seda("foo").customName("seda2")).to(mock("result"));

                from("direct:foo").to(seda("foo").customName("seda2"));
{code}

Where we use customName as new method where you can define a new name - eg I use seda2

> camel-endpointdsl - Specify component (bean) name without using uri
> -------------------------------------------------------------------
>
>                 Key: CAMEL-15049
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15049
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-activemq, camel-endpointdsl
>    Affects Versions: 3.2.0
>         Environment: spring boot 2.2.6
> camel 3.2.0
> java jdk 11
>            Reporter: aboudi rawas
>            Assignee: Claus Ibsen
>            Priority: Major
>              Labels: features
>             Fix For: 3.4.0
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> It is not so uncommon to have multiple ActiveMQComponent beans in projects I worked on.
> It is desirable to have an option to specify bean name in camel-endpoint dsl something like this way ( assuming that there exists two ActiveMQComponent, one called 'activemq' and the other called 'activemqservice' ).
> from(activemq("queueName").componentName("activemqservice"))
> Instead of just having the option to do this using URIs like
> from("activemqservice:queueName?...")...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)