[
https://issues.apache.org/jira/browse/CAMEL-12923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756376#comment-16756376
]
Marc Carter commented on CAMEL-12923:
-------------------------------------
chat:
BindingComponent is deprecated in favour of BindingNameComponent.
* xxx:queue:a.b.c
* binding:xxx:jms:queue:a.b.c
I can't find in code history or forums _why_ it was deprecated. Was it because
of the knowledge the binding definition must have of the delegate component
(xxx: -> jms: in the above example)? I think both styles have benefits and
ended up using the former for good reasons.
important bit:
The reported bug remains true of either model but is quite easy to correct by
re-adding the parsed params back onto the delegate URI using
{{URISupport.appendParametersToURI(delegateUri, parameters)}}
> BindingComponent support for endpoint parameters
> ------------------------------------------------
>
> Key: CAMEL-12923
> URL: https://issues.apache.org/jira/browse/CAMEL-12923
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.22.1
> Reporter: Marc Carter
> Priority: Minor
>
> Both BindingComponent and BindingNameComponent wrap a delegate Endpoint with
> some common contract. Neither support passing of URI parameters to their
> delegate and this critically limits their use.
> (/) binding:xxx:jms:queue:a.b.c
> (x) binding:xxx:jms:queue:a.b.c?preserveMessageQos=true
> {quote}org.apache.camel.ResolveEndpointFailedException: Failed to resolve
> endpoint: binding://xxx:jms:queue:a.b.c?preserveMessageQos=true due to:
> Failed to resolve endpoint: jms://queue:a.b.c?preserveMessageQos=true due to:
> There are 1 parameters that couldn't be set on the endpoint. Check the uri if
> the parameters are spelt correctly and that they are properties of the
> endpoint. Unknown parameters=[\{preserveMessageQos=true}]
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
