[
https://issues.apache.org/jira/browse/CAMEL-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629152#comment-13629152
]
Hadrian Zbarcea commented on CAMEL-6263:
----------------------------------------
I don't think the opening statement is correct. That is it is correct for some
endpoints and incorrect for others. There is an EndpointConfiguration interface
which is supposed to be the holder of configuration parameters, but the
components were not yet refactored to take advantage of it in a uniform manner.
I'd defer this until we cleanup the api for 3.0 (which is probably what was
intended anyway, as no 'fix version' was set).
> it'd be nice to be able to marshal a collection of endpoint objects to/from
> XML/JSON as configuration without custom mappings
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-6263
> URL: https://issues.apache.org/jira/browse/CAMEL-6263
> Project: Camel
> Issue Type: Improvement
> Reporter: james strachan
>
> endpoints are beans which contain a combination of configuration parameters
> (often primitive types) and runtime stuff.
> Since they are beans we should ideally be able to marshal them for
> configuration and DI purposes to and from XML/JSON. Though right now none of
> them tend to respect the use of transient fields / @JsonIgnore /
> @XmlTransient.
> It'd be good to add these to the core camel endpoints. I guess using
> 'transient' is the simplest then it should work with
> serialisation/JAXB/Jackson?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira