client persistent strategy using form

[Norbert Sándor <de...@erinors.com>]

Hi,

I would need a client property persistence implementation which stores the property values in the forms of the page (but not in other URLs).
Does anyone experienced with this?

BR,
Norbi

Re: client persistent strategy using form

[Norbert Sándor <de...@erinors.com>]

Sorry, I meant something like

@Persist(value="form")

My problem is that I use Hidden components for storing state but there are 
too many of them. So I'd like to use some more clever solution like custom 
property persistence.

BR,
Norbi

----- Original Message ----- 
From: "Jesse Kuhnert" <jk...@gmail.com>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Friday, November 04, 2005 12:45 PM
Subject: Re: client persistent strategy using form


Input type=hidden value=your property.

On 11/4/05, Norbert Sándor <de...@erinors.com> wrote:
>
> Hi,
>
> I would need a client property persistence implementation which stores the
> property values in the forms of the page (but not in other URLs).
> Does anyone experienced with this?
>
> BR,
> Norbi
>


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

Re: client persistent strategy using form

[Jesse Kuhnert <jk...@gmail.com>]

Input type=hidden value=your property.

On 11/4/05, Norbert Sándor <de...@erinors.com> wrote:
>
> Hi,
>
> I would need a client property persistence implementation which stores the
> property values in the forms of the page (but not in other URLs).
> Does anyone experienced with this?
>
> BR,
> Norbi
>