On Thu, 27 May 2010 23:26:13 -0300, Paul Stanton <p...@mapshed.com.au>
wrote:
I've also tried with @SessionState with no luck.
Please post your code. Without it, it will be very hard to understand
what's happening.
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
If componentB state is completely independent of componentA state when
using @Persist. In addition, if you have a component instance in one page
and another in another page, their state is independent, because,
ultimately, all @Persist handling is done per page. On the other hand, a
@SessionState private Class1 class1; is one for the whole session.
4. Ajax.Request to componentA via actionlink
> componentA.persistentField does NOT exist (problem)
What is responsible for evicting my session variable?
Again, please post your code.
Do I need to revert to HttpSession handling myself?
Only if you need to interact with some non-Tapestry code that uses the
session.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
