I've also tried with @SessionState with no luck.
I'm imagining it's because one request goes to componentA (where the
persistent field is) the other goes to componentB. The subsequent
request to componentA reveals that the persistent field is reset. ie:
1. Ajax.Request to componentA via actionlink
> componentA.persistentField does not exist, initialised
2. Ajax.Request to componentA via actionlink
> componentA.persistentField exists
3. Ajax.Request to componentB via manually constructed
> must be what resets the state
4. Ajax.Request to componentA via actionlink
> componentA.persistentField does NOT exist (problem)
What is responsible for evicting my session variable?
Do I need to revert to HttpSession handling myself?
Paul Stanton wrote:
Hi all,
I'm making a few different types of ajax requests on my page, and a
couple of fields on components and pages are annotated with
@Persist("session").
Some of the ajax requests are made via t:actionlink components, others
are via Ajax.Requests I've constructed myself (via
resources.createEventLink().toAbsoluteURI().
I've noticed that the value for the apparently persistent field is
reset to null when the second type of ajax requests are made ... this
may be because the actions point to different components as listeners.
I thought that marking @Persist("session") would mean their values
were stored in the HttpSession until session death or I specifically
set the value to null, regardless of which component/class is handling
the request ??
How do I achieve this if not by @Persist("session") ?
---------------------------------------------------------------------
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
