[TAP5-206] Document that you should not instantiate an @Persist field in its declaration

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.15
• Fix Version/s: 5.0.16
• Environment: N/A
• Assignee: Howard Lewis Ship
• Reporter: Dave Dombrosky
• Created: 17/Jun/08 18:43
• Updated: 06/Nov/08 23:04
• Resolved: 06/Nov/08 23:04

Description

Because of Tapestry's page pooling, persistent objects can behave in strange ways if not handled properly. Issues can arise when setting a value on a persistent property at the same time as declaring it.

I ran into this issue while doing something similar to this: http://www.nabble.com/Strange-behavior-when-instantiating-properties-directly-in-the-page-p17876779.html

I propose that a note is added to the User's Guide -> Persistent Data page to warn users of this potential issue.

Issue Links

• is duplicated by: TAP5-323 Fields marked with @Persist should not allow default values
• is related to: TAP5-321 Persisted field somehow shares its value across sessions.