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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.3, 5.4
• Fix Version/s: 5.4
• Component/s: tapestry-core
• Labels: parameters template
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 24/Mar/14 23:13
• Updated: 16/Apr/14 16:49
• Resolved: 16/Apr/14 16:49

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.