[
https://issues.apache.org/jira/browse/CAMEL-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004381#comment-16004381
]
Claus Ibsen commented on CAMEL-11096:
-------------------------------------
There is no such strict validation. The options listed in endpointOptions is
what gets generated in the JSon schema that represents the Camel component for
the connector (eg its all from Camel pov just a component). But at runtime you
can configure the connector as a Camel endpoint uri, and if you specify any
key=value pair that really exists in the real component then it works. We could
add such a check but I am not sure its worth it. By having it open we allow end
users to "fix" situations where they may need to set a special option that
exists in the real component but was not exposed in the connector.
So endpointOptions is more of a way to make the generated json schema and
meta-data files specify which options is intended to be used by end users /
tooling etc.
eg think it as a list of checkbox of the options where you can [x] which ones
you want to allow users to see and use.
> 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)
