camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CAMEL-5183) EndpointConfiguration - Looses parameters if there is a name clash with known tokens
Date Sun, 30 Nov 2014 15:16:12 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen reassigned CAMEL-5183:
----------------------------------

    Assignee: Claus Ibsen

> EndpointConfiguration - Looses parameters if there is a name clash with known tokens
> ------------------------------------------------------------------------------------
>
>                 Key: CAMEL-5183
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5183
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.9.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: Future
>
>
> The endpoint configuration introduced in Camel 2.9 introduces more issues than per see.
We should use the previous logic by default, and allow custom components to use a 3rd party
EndpointConfiguration if they need to.
> For example if you have a uri parameter named {{port}} then that is lost
> Given the test below it fails
> {code}
>     @Test
>     public void testConfigurationPortParameter() throws Exception {
>         EndpointConfiguration cfg1 = ConfigurationHelper.createConfiguration("mapped://foo:8080?one=true&two=2&port=123",
context);
>         String uri1 = cfg1.toUriString(EndpointConfiguration.UriFormat.Complete);
>         assertEquals("mapped://foo:8080?one=true&two=2&port=123", uri1);
>     }
> {code}
> There is other facts with this EndpointConfiguration that causes side-effects as the
previous logic was based on URISupport to parse the uris and whatnot. But the EndpointConfiguration
introduced a new logic for that, and they are not identical.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message