Re: [Springframework-developer] Spring Enhancement

[Rod J. <rod...@in...>]

+1 

> W/regards to backwards compatibility though, if strings that were 
> previously plaintext in existing elements like <value> were all of a 
> sudden interpreted as expressions, at a minimum people would have to go 
> through all the strings and suitably escape any values (like $) that 
> would trigger the expression evaluator. What would help in this respect 
> and also on the performance side, is to use a prefix on the string value 
> to indicate that it's an expression, e.g.
>    ognl:some.expression
> as Tapestry does, for example...