Add "initial-value" for unbounded components paramters (different from
"default-value")
---------------------------------------------------------------------------------------
Key: TAPESTRY-1700
URL: https://issues.apache.org/jira/browse/TAPESTRY-1700
Project: Tapestry
Issue Type: New Feature
Affects Versions: 4.1.2
Reporter: Martino Piccinato
I think it would be very useful and relatively easy to implement some kind of
"initial-value" attribute for unbound component parameters that, differently
from already existing default-value, would set an initial value on parameter
property instead of creating a new binding for it.
The "problem" with already existing default-value is that it express a binding
more than a value, actually a better name would have been "default-binding", I
know the documentation is clear but the name is very misleading. It always
create a binding and in some situations this is just an overhead, some other
time it seems not proper as all one wants to do is giving an initial value to
the component property without any binding because a constant binding (e.g.
ognl:true) would get in the way when changing the originally unbounded
parameter property.
I think this is exactly what happened with issue described in TAPESTRY-1699
that you can consider as a specific case where would be useful and clearer to
use this mechanism.
If you think this is a good idea I could provide some code for it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
