using Velocity to externalize configuration properties ?

[Brent Putman]

On 7/31/13 10:40 PM, Cantor, Scott wrote:
>
> That is one of the major issues, yes, and just generally things like
> controlling schema validation at all. It's just totally ridiculous to have
> Spring software not start up because their web site is down. It's one of
> those "what in the hell are they thinking?" issues.


Well, to be fair to them, it doesn't actually work that way when you use
it correctly.  All their schemas are local to their jars and they have a
proprietary XML catalog-ish mechanism which resolves those locally from
the classpath.

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?