You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2017/04/24 12:18:04 UTC

[jira] [Updated] (CAMEL-11190) Service Call - Allow to configure static server list from a property placholder

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

Claus Ibsen updated CAMEL-11190:
--------------------------------
    Fix Version/s: 2.20.0

> Service Call - Allow to configure static server list from a property placholder
> -------------------------------------------------------------------------------
>
>                 Key: CAMEL-11190
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11190
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.20.0
>
>
> Today you need to configure this per server
> https://github.com/camelinaction/camelinaction2/blob/master/chapter17/cluster-servicecall/client-static/src/main/java/camelinaction/MyStaticRouteGlobal.java#L17
> But you may want to externalize this in a .properties file and then refer to it such as
> {code}
> myservers=foo@server1,foo@server2,foo@server3,bar@server1,bar@server4
> {code}
> Where each entry is separated by comma.
> And then just refer to it with
> {code}
>  .staticServiceDiscovery()
>    .servers("{{myservers}}")
> {code}
> Also the parsing of the syntax with name@server is not as well documented. We should likely improve the code so it checks this syntax and reports to the user if its mis configured, eg people may just configure it as the hostname:port without specifying the name or vice-verse etc.



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