:[EMAIL PROTECTED]
>> Sent: Monday, December 31, 2007 10:01 PM
>> To: Tapestry users
>> Subject: Re: Displaying form data in Tapestry 5
>>
>> I believe this is covered in the tutorial.
>>
>> It is important that data that must survive from one request to
>
is Ship [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 31, 2007 10:01 PM
> To: Tapestry users
> Subject: Re: Displaying form data in Tapestry 5
>
> I believe this is covered in the tutorial.
>
> It is important that data that must survive from one request to
> another be sto
..
Thanks,
Yeeswar.
-Original Message-
From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
Sent: Monday, December 31, 2007 10:01 PM
To: Tapestry users
Subject: Re: Displaying form data in Tapestry 5
I believe this is covered in the tutorial.
It is important that data that must survive from
I believe this is covered in the tutorial.
It is important that data that must survive from one request to
another be stored in a field marked with @Persist. Tapestry manages
the HttpSession for you, triggered by the @Pesist annotation (and a
few others). Tapestry 5, like Portlets, uses seperate
do that...
>
> -Original Message-
> From: Joshua Jackson [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 26, 2007 3:24 PM
> To: Tapestry users
> Subject: Re: Displaying form data in Tapestry 5
>
> I think T5 has got the best Spring integration there is. I mean
, December 26, 2007 3:24 PM
To: Tapestry users
Subject: Re: Displaying form data in Tapestry 5
I think T5 has got the best Spring integration there is. I mean, the
integration between T5 and Spring is seamless. You can inject Spring
bean into T5 just you would inject a T5 bean/components. The
I think T5 has got the best Spring integration there is. I mean, the
integration between T5 and Spring is seamless. You can inject Spring
bean into T5 just you would inject a T5 bean/components. The
configuration is also very small in web.xml
I think T5 with Spring is the best deal out there.
On 1
