Property syntax collision
Cantor, Scott
cantor.2 at osu.edu
Mon Jun 23 16:07:36 EDT 2014
On 6/23/14, 3:24 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
>
>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.
Doing this globally appears to work fine. Tests all run, etc.
Of course, web.xml is an exception, that still has to use ${} because I
don't think we control the configurer that's being used there, but I
suppose we could override that somehow if we cared enough. For alpha
purposes, I'm just worried about things functioning.
Having not seen any comments, I'll hold off checking in a fix since it
hits lots of the Spring files.
-- Scott
More information about the dev
mailing list