Re: [T5.0.6] Is coercion MANDATORY for custom parameter classes? [BUG?]

[Vjeran Marcinko <vj...@email.t-com.hr>]

----- Original Message ----- 
From: "César Lesc" <ce...@gmail.com>
To: "Tapestry users" <us...@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
> declare the binding in the template?.

Just normally :

Start.tml :

<t:imagemessage t:model="imageMessageModel"/>

And of course, Start.java contains :

public ImageMessageModel getImageMessageModel() {
    return new ImageMessageModel(Type.ERROR, "some error");
}

Can this be a bug due to some classloading issue ?

Regards,
Vjeran


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

Re: [T5.0.6] Is coercion MANDATORY for custom parameter classes? [BUG?]

[César Lesc <ce...@gmail.com>]

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 parameter as
    @Parameter(required = true)
    private UserSession user;

and the layout component class define the getter as

    public UserSession getUser() {
        return userSession;
    }

userSession is a ASO and is instantiate in the log in process but i
don't think that matters.


Cesar.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org