[jira] Commented: (CAMEL-2248) Make endpoint URI reference parameter handling code more consistent across components

["Martin Krasser (JIRA)" <ji...@apache.org>]

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

Martin Krasser commented on CAMEL-2248:
---------------------------------------

The current implementations of 

* {{DefaultComponent.resolveAndRemoveReferenceParameter}} and
* {{DefaultComponent.resolveAndRemoveReferenceParameterList}}

will be changed to:

* make usage of leading # for references optional
* make bean reference lookups in the registry mandatory

This will support backwards-compatibility to existing endpoint URIs. For example

* in the jetty component, usage of a leading # for the handlers parameter is optional
* in the http component, usage of a leading # for the {{httpBindingRef}} parameter was not even possible so far. 
 
Instead of breaking a potential high number of existing client applications (by forcing them to use a leading #), changing these two methods will likely not cause any issues when upgrading to Camel 2.2.

Furthermore, making a mandatory lookup of referenced beans (i.e. throwing an exception instead of returning null if not found) will make it much easier to detect typos in reference names and is more consistent with existing reference handling code.


> Make endpoint URI reference parameter handling code more consistent across components
> -------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2248
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2248
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-http, camel-jdbc, camel-jetty, camel-jms, camel-spring
>    Affects Versions: 2.1.0
>            Reporter: Martin Krasser
>            Assignee: Martin Krasser
>            Priority: Minor
>
> Components that resolve reference parameters should consistently use the methods {{DefaultComponent.resolveAndRemoveReferenceParameter}} and {{DefaultComponent.resolveAndRemoveReferenceListParameter}}

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