Tapestry 5
  1. Tapestry 5
  2. TAP5-1675

Tapestry 5.3 allows a subcomponent to define a parameter with the same name as a base component

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 5.3
    • Fix Version/s: 5.3
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      I believe you got a more reasonable error message in 5.2. In 5.3 you may get an error if both the fields have @Property, due to a name collision on the getter/setter method names. Instead, Tapestry should fail early explaining that both the component and (the identified base class) define the same parameter name.

        Activity

        Howard M. Lewis Ship made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Assignee Howard M. Lewis Ship [ hlship ]
        Fix Version/s 5.3 [ 12316024 ]
        Resolution Fixed [ 1 ]
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Summary Tapestry 5.3 allows a subcomponent to defined a parameter with the same name as a base component Tapestry 5.3 allows a subcomponent to define a parameter with the same name as a base component
        Howard M. Lewis Ship created issue -

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development