[jira] [Created] (TAP5-2306) Mixin parameters should be qualified (with the new 5.4 DTD)

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

Howard M. Lewis Ship created TAP5-2306:
------------------------------------------

             Summary: Mixin parameters should be qualified (with the new 5.4 DTD)
                 Key: TAP5-2306
                 URL: https://issues.apache.org/jira/browse/TAP5-2306
             Project: Tapestry 5
          Issue Type: Bug
          Components: tapestry-core
    Affects Versions: 5.3, 5.4
            Reporter: Howard M. Lewis Ship


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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)