Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-2306

Mixin parameters should be qualified (with the new 5.4 DTD)

    Details

      Description

      Tapestry's current behavior, with the 5.3 DTD (and the current 5.4 DTD) is that parameters are matched against any mixin, or the component, with a formal parameter.

      A problem exists when a mixin has a formal parameter and the component (or other mixin) supports informal parameters; the mixin will "take" the unqualified attribute as a parameter.

      I think a better solution would be to require that mixin parameter names be fully qualified, always.

      Of course, there's more ambiguity in the Component annotations's parameters parameter.

      I would suggest that parameters be added to the Mixin annotation, and it should be used inside a Mixins annotation.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: