[
https://issues.apache.org/jira/browse/CAMEL-16221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17388555#comment-17388555
]
Claus Ibsen commented on CAMEL-16221:
-------------------------------------
You can build those uris today via ExtendedCamelContext, where context-path and
query parameters are assembled correctly (such as your http and infinispan
example)
{code}
getEndpointUriFactory("http").buildUri("http", map goes here);
{code}
> Rethink endpoints URI usage for camel internals
> -----------------------------------------------
>
> Key: CAMEL-16221
> URL: https://issues.apache.org/jira/browse/CAMEL-16221
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Luca Burgazzoli
> Priority: Major
> Fix For: 3.x
>
>
> As today URIs are the primary mechanism Camel uses internally to describe
> endpoints but I think it is time to re-consider the dependency on URIs for
> camel internals and leave the URIs as an external representation of endpoints
> As example:
> - the Endpoint DSL is required to generate the related endpoint URI to
> leverage Camel's APIs but to create an endpoint, the schema and a map of
> options, would be more than enough.
> - components that wrap other components, such as kamelets, master & co may
> need to re-create URIs to create instances of the delegated endpoints which
> is cumbersome as there's lot of options to take into account (RAW,
> url-encoding, placeholders)
> - the YAML DSL and camel-kafka-connectors are using and Endpoint DSL alike
> syntax where a user can define endpoints by scheme + option pairs without the
> need of writing URIs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
