Property syntax collision

[Cantor, Scott]

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

>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.

That's the older classname, but updating that part, this seems to work:

<bean 
class="org.springframework.context.support.PropertySourcesPlaceholderConfig
urer"
	p:placeholderPrefix="%{"
	p:placeholderSuffix="}" />

At least for the basic Spring files. I'd need to do more testing on the
webflow portions and make sure there's no gotcha, but this seems to be the
substitute that works around the conflict.


Does this overly concern anybody? I don't see that we have a lot of choice
here regardless of how it clashes with Spring convention.

The alternative is just to not do properties in the files that might have
Velocity snippets in them, but that's probably unworkable in the long run
unless we just stop using Velocity as the macro language for those things.

-- Scott