-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
To point 1: I noticed this change as well and I must say I agree that the literal should take precedence. I understand that "if you use non-literal, it's probably ognl", but that can tend to be a big 'if'. And to be honest - if it's enclosed in quotes, it appears as though you should be able to accept it as a string, not an expression.
What I would propose - and it impacts configuration code more than anything - is the following: ~ 1. Literal is the default ~ 2. Configuration can override the default
What I mean by this is - with 0 changes to any configuration anywhere - if you type <set name="pattern" value="MM-dd-yyyy"/>, that's what you get - literal - as it's the default. If you go into your configuration, however, you can specify (possibly via a service?) default-binding="ognl", default-binding="???" - let the 'default' be the user's to decide. A related change would be to allow configuration of what prefix is mapped to which binding - specify 'o' for 'ognl', but that's outside the scope of what you brought up (and might prove cumbersome for utilizing outside component libraries).
For point 2 I have no thoughts either way, but do understand the extra work.
Brian
Paul Ferraro wrote: | I would like to discuss 2 issues relating to binding prefixes: | 1. In alpha-1 (or maybe earlier), I recall that the default binding | prefix for bean properties was changed to "literal". I saw this as an | improvement over 3.1. In alpha-2, this was changed back to "ognl". | I think I liked it better the other way around. I dislike having to use | nested quotes to define literal strings this way within an xml attribute | (e.g. <set name="pattern" value="'MM-dd-yyyy'"/>). | Can we switch this back? | | 2. The more I use 4.0, the more I find the default binding prefix | override for component parameters to be incredibly frustrating. I think | that the hassle of having to lookup (or remember) the expected binding | prefix for each component parameter far outweighs the minimal keystroke | savings. I liked it better when "literal" was the default and | overriding was not permitted. Things were much more straight forward | that way. I find that I am wasting a lot of time debugging runtime | exceptions in my component specification because I assumed the wrong | binding prefix. | | Thoughts? | | Paul | | | --------------------------------------------------------------------- | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | | | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32)
iD8DBQFCexTQaCoPKRow/gARAoUaAKDk3kI+rx3Xc3Wj5ANueQg8GM2LXQCfdmEi 6DsUk2xrwLgbqxqMHJKvQkw= =PWwT -----END PGP SIGNATURE-----
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
