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. org.apache.commons.configuration.Configuration could be used as a model and eventually some things could be dropped(like sub-configurations?)

Thanks.

On 11/29/2010 01:20 PM, Nathan Bubna wrote:
I haven't looked at commons configuration in years.  I'm randomly
perusing it now.  I like what i see.  It does seem a bit heavy, but i
suppose it provides a lot more config options than we currently do.
Considering Engine's position as a library/component project, that's a
plus.  Let people configure as they need.  I also like their support
for configuration events; interesting possibilities there.

On Mon, Nov 29, 2010 at 6:46 AM, Antonio Petrelli
<[email protected]>  wrote:
Hi all
I noticed that, in Velocity Engine, the dependency on Commons
Collections is due to the use of ExtendedProperties and LRUMap.

I know what to do with LRUMap (shade the needed classes of Commons
Collections), however I think ExtendedProperties could be replaced
with Commons Configuration. So, if we want, we can move from simple
properties files to other types (e.g. XML, servlet parameters) with no
extra effort. Moreover Commons Configuration allows loading multiple
sources: this is important to me since I would like to implement,
later, the ability to load configuration from multiple files (for
example to load user directives from various JARs automatically,
without configuration).

WDYT?

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]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to