using Velocity to externalize configuration properties ?

[Tom Zeller]

> As I've mentioned before, the problem is that in V2, our Spring custom
> XML parsing is conceptually horked.  Chad made a major brain fart there,
> but it "works" because we install a custom entity resolver that is
> broken in the same way.  I discovered this quite awhile after V2
> shipped, so it was took late to change it.
>
> I haven't really been following all the XML parser work that we've been
> doing for V3, but perhaps now is a good time to review that we aren't
> replicating what was horked in V2.  Perhaps a topic for the call tomorrow?

Sure. I know I have asked before, but I'll need to be reminded
regarding the details of the incorrect v2 behavior.