commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <>
Subject [jira] Resolved: (CONFIGURATION-196) [configuration] Tools for code generation of configuration properties
Date Fri, 02 Feb 2007 19:55:06 GMT


Oliver Heger resolved CONFIGURATION-196.

       Resolution: Won't Fix
    Fix Version/s: 1.4

I am still on the opinion that this suggestion is out of scope for Commons Configuration.
No other committer chimed in, so I am closing this ticket as won't fix.

If you are still interested in this topic, maybe you can start a project elsewhere (e.g. sourceforge)
that builds upon Commons Configuration. In any case thanks for your interest.

> [configuration] Tools for code generation of configuration properties
> ---------------------------------------------------------------------
>                 Key: CONFIGURATION-196
>                 URL:
>             Project: Commons Configuration
>          Issue Type: Improvement
>    Affects Versions: 1.1
>         Environment: Operating System: other
> Platform: Other
>            Reporter: David Leal
>            Priority: Minor
>             Fix For: 1.4
> I would like to just suggest a kind of code generation from a defined 
> properties/xml file, so the user can avoid the use of string representing the 
> properties on whole source code. For example if I have the following property:
> ftpServer.login = anonymous
> in order to get the value of such property, instead of:
> getProperty("ftpServer.login");
> to have an equivalente class representation, like this:
> getFtpServer().getLogin();
> or just:
> ftpServer().getLogin();
> with this solution, you avoid miss-spelling of the property name (for example: 
> instead of "ftpServer.loging", "ftpserver.login"), because you will get a 
> compiler error.
> in order to get this target we need a kind of code generation of the 
> corresponding classes. Like any other generation tools it should be a mapping 
> file for configuring the way the properties/subproperties/nodes could be 
> mapped, for example tomorrows I would like to map: ftpServer.login to getServe
> ().getLogin(). With the default configuration the mapping will be the same.
> It could be just and ant-taks for doing this, probably with velocity would be 
> easy to implement.
> Thanks in advance,
> David Leal
> (If you want I could colaborate)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message