[TAPESTRY-320] "client" persistent properties are shared between users

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0
• Fix Version/s: 4.0
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 10/May/05 21:38
• Updated: 10/May/05 22:27
• Resolved: 10/May/05 22:27

Description

This is caused by a number of factors:

• The service model for tapestry.persist.ClientPropertyPersistenceStrategy was primitive, not threaded
• The initialize method was not named properly

The end result is that a single ClientPropertyPersistenceStrategy instance was being shared between all users, so that changes to state by one user would be seen in later requests by all users.