@Prefix annotation on interfaces for keys about owner

[lviggiano]

I like both, the @KeyPrefix and the variable expansion in the @Key annotation. And they should be easy to implement.

[lviggiano]

In particular, consider a property file like this

# Production settings
prod.service.endpoint=http://productionserver:80

# Development settings
dev.service.endpoint=http://developmentserver:8080

# User acceptance test settings
uat.service.endpoint=http://testserver:8080

One could have a class like:

interface MyConfig extends Config {

    @Key("${environment}.service.endpoint")
    URL serviceEndpoint();

}

Where ${environment} can be passed from outside at creation time (ConfigFactory) or by System properties, to have a single file that configures different deployment environments. The variable expansion already works in the @sources and this can be implemented using different files, but also giving the user the chance to have a single properties file defining all the environments could be good, from the user perspective.

[binkley]

This fits my use case perfectly. Thanks!

[binkley]

You might appreciate - http://binkley.blogspot.com/2013/10/better-java-properties-handling.html.

[lviggiano]

Yes, very much :) I noticed it the other day.

[binkley]

Here's the kind of simple application I want to write, using OWNER API and
jopt-simple, glued with Guice:

https://github.com/binkley/binkley/blob/develop/guice/src/main/java/hm/binkley/inject/DemoMain.java

Cheers,
--binkley

On Sun, Oct 13, 2013 at 9:25 PM, Luigi R. Viggiano <[email protected]

wrote:

Yes, very much :) I noticed ithttps://twitter.com/lviggiano/status/388639933524504576the other day :)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/56#issuecomment-26215146
.

[lviggiano]

👍 (I'll work on this request asap: those day I started a new job contract, so I've been very busy)