Property syntax collision

[Cantor, Scott]

On 6/23/14, 4:25 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

>On 6/23/14, 4:18 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>
>>> 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.

And it's not true, it will actually pass through the unresolved ones so
they don't get molested.

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

So that's still my main argument in favor of changing the delimeter, but
I'm fine if others disagree and would rather we just set the
ignoreUnresolvable property and leave Spring's syntax alone.

-- Scott