Perhaps it would simplify things then to make template bindings always
use literal prefix by default, but allow specification bindings to
default differently. That way the template bindings would work the same
as Tapestry 3.
Richard
Paul Ferraro wrote:
I added this issue in response to a problem a user encountered
converting from 3.0 to 4.0. People seemed surprised that the tag
parameter expected an ognl expression and not a literal. I think the
larger issue is that users are finding default bindings to be a source
of confusion. Especially since every parameter in 3.0, including
informal ones, were literal unless otherwise indicated. Some users have
taken to *always* using a binding prefix - so it appears that this
feature is not entirely successful since it's intent was to save
keystrokes. Thoughts?
Paul
Richard Lewis-Shell (JIRA) wrote:
[
http://issues.apache.org/jira/browse/TAPESTRY-336?page=comments#action_66425
]
Richard Lewis-Shell commented on TAPESTRY-336:
----------------------------------------------
I am not sure this is a good idea. All the time of time I have used
tag I've used it to select a real object, not just a String. Just me?
Change default binding of "tag" parameter in Submit component to
"literal"
--------------------------------------------------------------------------
Key: TAPESTRY-336
URL: http://issues.apache.org/jira/browse/TAPESTRY-336
Project: Tapestry
Type: Improvement
Components: Framework
Versions: 4.0
Reporter: Paul Ferraro
Priority: Minor
The default binding of the "tag" parameter in the Submit component
should be changed from "ognl" to "literal" since it is usually bound
to a literal string.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
