Tapestry
  1. Tapestry
  2. TAPESTRY-1700

Add "initial-value" for unbounded components paramters (different from "default-value")

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 4.1.2
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Martino Piccinato
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development