|
|
Hi everyone,
the instructions on the Tapestry project site say that changes made to
mutable objects used as ASOs may possibly not be propageted to all nodes
of a clustered application, depending on how the ApplicationServer
handles the clustering.
What is the best way to make sure that changes are replicated?
Example: I store a list of Strings and add new Strings during the course
of a request. Is it enough to call applicationStateManager.store() again
to store the same instance und the same old name it's already stored in?
Thanks,
MARK
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: tapestry-user-help@xxxxxxxxxxxxxxxxxx
|
|