You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Ashish Raniwala <ar...@gmail.com> on 2005/06/08 07:19:22 UTC
Binding directions limitation
Hi Guys,
I remember reading limitations of binding directions somewhere but not able to find it now.
I am facing problem with 'in' direction and parameter does not get parameter value during component rendering.
Changing to direction auto works fine.
Can anyone please point me to some resource where I can read about limitations on binding directions?
Thanks in advance.
Regards,
Ashish
Re: Binding directions limitation
Posted by Robert <rv...@xs4all.nl>.
Robert Zeigler wrote:
>Robert wrote:
>
>
>And, in version 4.0/Picasso: there is no more "direction". :)
>
>Robert
>
>
>
Wow good news. Is there any release date yet? Will it be this year?
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Binding directions limitation
Posted by Robert Zeigler <ro...@scazdl.org>.
Robert wrote:
> Ashish Raniwala wrote:
>
>> Hi Guys,
>> I remember reading limitations of binding directions somewhere but not
>> able to find it now. I am facing problem with 'in' direction and
>> parameter does not get parameter value during component rendering.
>> Changing to direction auto works fine. Can anyone please point me to
>> some resource where I can read about limitations on binding directions?
>> Thanks in advance.
>> Regards,
>> Ashish
>>
>>
> From Tapestry in Action:
> - in: Only available during rendering. Doesn't update.
> - form: For form-elements. Read when rendering. Updated when submitted.
> -auto: Can be read and updated when you like. Must be required
> parameter. Of primitive types only boolean, int and double are supported.
> - custom: Leaves control in your hands.
And, in version 4.0/Picasso: there is no more "direction". :)
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Binding directions limitation
Posted by Robert <rv...@xs4all.nl>.
Ashish Raniwala wrote:
>Hi Guys,
>I remember reading limitations of binding directions somewhere but not able to find it now.
>I am facing problem with 'in' direction and parameter does not get parameter value during component rendering.
>Changing to direction auto works fine.
>Can anyone please point me to some resource where I can read about limitations on binding directions?
>Thanks in advance.
>Regards,
>Ashish
>
>
From Tapestry in Action:
- in: Only available during rendering. Doesn't update.
- form: For form-elements. Read when rendering. Updated when submitted.
-auto: Can be read and updated when you like. Must be required
parameter. Of primitive types only boolean, int and double are supported.
- custom: Leaves control in your hands.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org