camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luca Burgazzoli (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CAMEL-11096) Connector semantics with respect to default values
Date Wed, 10 May 2017 09:24:04 GMT

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

Luca Burgazzoli edited comment on CAMEL-11096 at 5/10/17 9:23 AM:
------------------------------------------------------------------

Ok so options outside endpointOptions are not supposed to be overridden by the user correct
? 
i.e. if there is something in endpointValues which is not in endpointOptions and the user
provides it --> component failure
i.e. in this case if a user sets operationName there should be a failure


was (Author: lb):
Ok so options outside endpointOptions are not supposed to be overridden by the user correct
? 
i.e. if there is something in endpointValues which is not in endpointOptions and the user
provides it --> component failure

> Connector semantics with respect to default values
> --------------------------------------------------
>
>                 Key: CAMEL-11096
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11096
>             Project: Camel
>          Issue Type: Task
>          Components: camel-connector
>    Affects Versions: 2.19.0
>            Reporter: Roland Huss
>            Priority: Minor
>
> I would like to discuss the semantics of default parameters for connectors. Currently
a user can override 'frozen' (== pre-configured) component options when [creating the endpoint|https://github.com/apache/camel/blob/bc9d07700678604ae43754a32519898c47bb9529/connectors/camel-connector/src/main/java/org/apache/camel/component/connector/DefaultConnectorComponent.java#L261]
> I wonder whether this is the desired behaviour ? E.g. when creating a `salesforce-upsert-connector`
and letting override the "operationName" (which was preconfigured in the connector) defeats
its purpose imo. (Although it was just quite helpful in my case ;-)
> Of course the ideal solution would be to mark options as overridable or not.
> What do you think ?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message