[
https://issues.apache.org/jira/browse/CAMEL-11410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050215#comment-16050215
]
Aurelien Pupier edited comment on CAMEL-11410 at 6/15/17 9:21 AM:
------------------------------------------------------------------
What is the process to provide a warning in the release notes?
it might be useful to provide one warning to users which were relying on this
feature that they now need to put "registerEndpointIdsFromRoute" attribute to
true (or to use an "endpoint"). What do you think?
was (Author: aurelien.pupier):
What is the process to provide a warning in the release notes?
it might be useful to provide one warning to users which were relying on this
feature that they now need to put "registerEndpointIdsFromRoute" attribute to
true. What do you think?
> camel-spring - Should not list uris as spring bean ids from Camel routes
> ------------------------------------------------------------------------
>
> Key: CAMEL-11410
> URL: https://issues.apache.org/jira/browse/CAMEL-11410
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.20.0
>
>
> Its an old and unused feature of Camel that will register endpoint in spring
> from routes from the <from> and <to> if they have an id attribute assigned.
> Those id's was not as much intended for that, as you can have endpoints in
> other places in routes, such as <wireTap> etc.
> Users should use <endpoint id="xxx"> to assign id's to endpoint in case they
> want to refer to those from Spring, such as via dependency injection.
> This functionality is also only in camel-spring and not in camel-blueprint,
> so it only adds to confusion if the XML DSL do not behave as much similar as
> possible.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
