Hi all,
I found a nasty situation where some xhr requests were running into
nullpointers on properties of persistent page properties/fields. My
theory being that there is some access to fields of a persistent field
in XHR request A, while XHR request B is still setting the values for
the field.
I always assumed that tapestry 5.x handled thread safety for you?
"Tapestry also shields you from the multi-threaded aspects of web
application development. Tapestry manages the life-cycles of your page
and components objects, and manages the fields of the pages and
components in a thread-safe way. Your page and component classes always
look like simple, standard POJOs."
I had assumed this meant that multiple XHR requests from the same
session would be queued up and processed one at a time on the server.
This appears to not have been the case, and now having every XHR event
listener synchronized on the session I no longer seem to get the problems.
Could someone clarify what is meant by the above quote and whether it
applies to 5.1.x or just 5.2+?
Also, is my approach of synchronization using the session object the
best solution here?
Thanks, Paul.
ps I'm stuck on tapestry 5.1.0.5 for this project.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
