Antonie,
What I wanted to say is to follow the model and not to include any
dependency. A minimal functionality should be to set/get primitive types
and work with lists and store everything behind as strings(with "," as
separator for lists). I do not thing there is a need for anything else
then storing bools(is feature A enabled/disabled), ints, strings and
list of strings for Velocity.
On 11/29/2010 02:05 PM, Antonio Petrelli wrote:
2010/11/29 Adrian Tarau<[email protected]>:
I would really like to see the configuration as an interface and provide
factories to create a configuration based on a simple Map or Jakarta Commons
Configuration(or something else).
This would allow any developer to inject their own configuration into
Velocity without the need to pass around values.
Good idea! The real configuration implementation will go to a
different module then.
org.apache.commons.configuration.Configuration could be used as a model and
eventually some things could be dropped(like sub-configurations?)
I think it's better to have a Velocity-specific configuration as an
interface and an implementation that uses Commons Configuration.
This can be a later step though. Adding an interface will remove the
dependency on ExtendedProperties, that will go into a new module.
Thanks.
Thanks to you
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
