I'm currently evaluating component based frameworks, as we are using
Wicket, and one of the problems we encounter is Ajax interactions after the
http session has expired.

If a user clicks on a component that is Ajax enabled - the framework throws
a PageExpiration exception.

For most applications, we want the request to still continue.

The HelloWorld example from Tapestry doesn't appear to experience this.

My questions are

- For persistent data on a page where is this serialized to?
- Are all Ajax interactions safe in this manner, form buttons, links, etc

Reply via email to