tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laurent Guerin (JIRA)" <j...@apache.org>
Subject [jira] [Created] (TAP5-1642) Mixins parameters with required=true and default value provided
Date Mon, 12 Sep 2011 21:53:08 GMT
Mixins parameters with required=true and default value provided

                 Key: TAP5-1642
                 URL: https://issues.apache.org/jira/browse/TAP5-1642
             Project: Tapestry 5
          Issue Type: Bug
          Components: tapestry-core
    Affects Versions: 5.3
            Reporter: Laurent Guerin

In our Tapestry 5 library (exanpe-t5-lib), we provide some mixins containing some parameters
declared as "required=true" AND with a default value.
These parameters are required for the operation of the mixin.

For example, in a Dialog mixin, we have :

    @Parameter(value = "confirm", required = true, allowNull = false, defaultPrefix = BindingConstants.LITERAL)
    private DialogRenderModeEnum renderMode;

If this required parameter is not explicity bound in the TML :
- In 5.2.6, everything is ok : the default value is used
- In 5.3-beta-5, we get the following Exception :
      Parameter(s) 'Dialog.renderMode' are required for org.apache.tapestry5.corelib.components.ActionLink,
but have not been bound.

The TML example looks like this :
<t:actionlink t:id="link1" t:mixins="exanpe/dialog">link1</t:actionlink>

With a simple type for mixin parameter (Integer or String), the same error occurs.
This behavior is only for mixins, not for components.

A simplified project that duplicates the issue has been attached : the mixin Emphasis used
into Index.tml is ok in 5.2.6 and ko in 5.3.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message