Property syntax collision

[Cantor, Scott]

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

>I ran into the first major "oh, that's a bug" with the alpha code: we have
>a collision between Spring property syntax and the Velocity syntax we rely
>on for things like Template attribute definitions, eg.

It's possible we can fix this by using a custom bean for the
PropertyPlaceholderConfigurer instead of using the <context> namespace to
shorthand it.

There are prefix and suffix properties on that class that seem to be the
source of the ${ and } character delimiters it's parsing.

I don't think Velocity has the same flexibility, but I'm looking.

It's not terribly attractive to do this, but I'm not sure there's much
choice. Even if Velocity could be overridden somehow, that breaks all the
existing Template expressions and SQL statements and so forth in existing
V2 files, whereas we have no extant Spring properties to break.

I'd tentatively say we should shoot for %{} as a syntax if it works.

We could of course override this just in cases where this conflict occurs,
but that seems like a bad idea.

-- Scott