- Original Message -
From: César Lesc [EMAIL PROTECTED]
To: Tapestry users users@tapestry.apache.org
Sent: Friday, November 16, 2007 5:57 PM
Subject: Re: [T5.0.6] Is coercion MANDATORY for custom parameter classes?
You don't have to create a coercion for you custom class, how do you
You don't have to create a coercion for you custom class, how do you
declare the binding in the template?.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
That's weird, i do the same but in a component template, and have no problems
I have a MenuItem that will render for certains users but not for others.
then my layout template define the menuItems as follow
...
li t:type=MenuItem user=user
...
the MenuItem component define the user
]
To: Tapestry users users@tapestry.apache.org
Sent: Friday, November 16, 2007 8:35 PM
Subject: Re: [T5.0.6] Is coercion MANDATORY for custom parameter classes?
you must move any class that is not page or componenta from
base, components, pages packages
they get enhanced and those exceptions occur
http
Hello.
Still getting acquainted with T5, and I created my first component called
ImageMessage that accepts my custom ImageMessageModel parameter:
public class ImageMessage {
@Parameter(required = true)
private ImageMessageModel model;
}
And when I bound my ImageMessageModel
you must move any class that is not page or componenta from
base, components, pages packages
they get enhanced and those exceptions occur
http://wiki.apache.org/tapestry/Tapestry5HowToNotMakeCustomComponent
Davor Hrg
On Nov 16, 2007 5:57 PM, César Lesc [EMAIL PROTECTED] wrote:
You don't have
