Ups .-.. thanks .. i might need to re-read the documentation again :)
From the docs:
Assigning a value to an SSO field will store that value. Assigning
null to an SSO field will remove the SSO (reading the field
subsequently will force a new SSO instance to be created).
Uli
On 14.07.2009 13:21 schrieb jose luis sanchez:
Hello.
I'm using a Session Object to store the data in a multipage creation
wizard.
After the last screen, th3e object is persisted in database, so i no
longer need it.
The problem arises when i hit again the "add new object" button, and
the fields keep the previous data ... because the SSO is still inmemory.
Is there anyway to get rid of this behaviour ?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
