using Velocity to externalize configuration properties ?

[Marvin Addison]

> I believe the idea is to use Velocity similar to the v2
> PropertyReplacement ResourceFilter. The Spring
> PropertyPlaceholderConfigurer also seems relevant.

I just finished retooling our configuration using ResourceFilter. I
was able to do everything I wanted and the property replacement
approach generally is very flexible. I encourage you to look at the
new "environment" configuration available in Spring 3.2, which pulls
from a number of sources including system properties, servlet context,
and properties files in a hierarchical fashion with the usual
${property} syntax. It's very powerful and it would be great to simply
expose the Spring capabilities either directly or through a
lightweight adapter layer.

I guess I'm wondering what sorts of things you could do with Velocity
that you can't do with the existing capabilities. Relatedly, I'm
wondering whether advanced configuration features encourages bad
habits.

M