You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "John D. Ament (JIRA)" <ji...@apache.org> on 2016/04/16 14:39:25 UTC
[jira] [Commented] (DELTASPIKE-1126) variable support in
ConfigResolver
[ https://issues.apache.org/jira/browse/DELTASPIKE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244196#comment-15244196 ]
John D. Ament commented on DELTASPIKE-1126:
-------------------------------------------
Since this is a new feature, should it be 1.6.1?
> variable support in ConfigResolver
> ----------------------------------
>
> Key: DELTASPIKE-1126
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1126
> Project: DeltaSpike
> Issue Type: New Feature
> Components: Configuration
> Affects Versions: 1.6.0
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.6.1
>
>
> I'd like to implement the following feature in ConfigResolver:
> {code}
> myapp.someapp.soap.endpoint=${someapp.host.url}/someservice/myendpoint
> {code}
> and
> {code}
> someapp.host.url=http://localhost:8081
> {code}
> Of course this is a behaviour which needs to be enabled for each config resolving.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)