t.zeig...@roxanemy.com]
> Envoyé : lundi 12 septembre 2011 17:35
> À : Tapestry users
> Objet : Re: Possible bug in 5.3 with Mixin parameters
>
> Sounds like a bug. If you can create a simplified project (eg: 1 page, 1
> mixin) that duplicates the issue, then create a Jira and atta
Thanks, i'll try to create a simplified project quickly and file a JIRA.
-Message d'origine-
De : Robert Zeigler [mailto:robert.zeig...@roxanemy.com]
Envoyé : lundi 12 septembre 2011 17:35
À : Tapestry users
Objet : Re: Possible bug in 5.3 with Mixin parameters
Sounds like
-Message d'origine-
De : Josh Canfield [mailto:joshcanfi...@gmail.com]
Envoyé : lundi 12 septembre 2011 17:34
À : Tapestry users
Objet : Re: Possible bug in 5.3 with Mixin parameters
On Sep 12, 2011 8:23 AM, "Guerin Laurent" wrote:
>
> Hi all,
>
> In our Ta
Sounds like a bug. If you can create a simplified project (eg: 1 page, 1
mixin) that duplicates the issue, then create a Jira and attach the project.
Robert
On Sep 12, 2011, at 9/1210:18 AM , Guerin Laurent wrote:
> Hi all,
>
> In our Tapestry 5 library (exanpe-t5-lib), we provide some mixins
On Sep 12, 2011 8:23 AM, "Guerin Laurent" wrote:
>
> Hi all,
>
> In our Tapestry 5 library (exanpe-t5-lib), we provide some mixins
containing some parameters declared as "required=true" AND with a default
value provided.
What do you mean by default value? Are you providing a defaultRenderMode
met
Hi all,
In our Tapestry 5 library (exanpe-t5-lib), we provide some mixins containing
some parameters declared as "required=true" AND with a default value provided.
These parameters are required for the operation of the mixin.
For example, on Dialog mixin, we have :
@Parameter(value = "confi
