Richard Lewis-Shell: -1 (binding)
It is not clear to me that we have exhausted other possibilities to
reduce confusion. Removing the feature seems pretty heavy handed. If
it was deemed that defaults were not so good for the framework, then an
alternative idea would be to make all framework parameters use OGNL but
allow other people/components to use defaults if they want to. (this
might actually be what the vote was for - that is also not clear to me)
eg. why not make template bindings always use literal unless otherwise
specified. This is backwards compatible with 3.0 which is where this
original problem came from - pain+confusion when upgrading to 4.0.
Howard Lewis Ship wrote:
I actually favor default-binding, I think it "looks nice", but it
seems to be causing a lot of confusion, and may violate the
"Consistency" principle. When in doubt ... vote; we'll see what the
majority states.
Howard M. Lewis Ship: -0 (binding)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
