Property syntax collision

[Tom Zeller]

>>> It of course crashes at startup on the undefined property. Oops.
>>
>>Just tossing out an idea : should override Spring to not bail on
>>startup on unresolvable properties ? Don't know how to or if it is
>>possible at the moment.
>
> It is possible. That would be done in a similar manner, with a custom
> bean. But I think what that will do is just replace the Velocity markers
> with nothing, which breaks us obviously. I didn't test that assumption.

Oh, forgot, that toggle is ignoreUnresolvablePlaceholders. I was
thinking the unresolvable placeholder would remain intact for Velocity
to handle.

> My concern also was just the error-prone result of ignoring macro mistakes
> when the other fix doesn't create that problem.

Right, agree.