[TAP5-323] Fields marked with @Persist should not allow default values

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.16
• Fix Version/s: 5.0.16
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Yunhua Sang
• Created: 03/Nov/08 17:09
• Updated: 06/Nov/08 23:11
• Resolved: 06/Nov/08 23:11

Description

An error should be raised when a persistent field comes with inline mutable object initialization, cause the result is very surprised: the field is not in session boundary, instead visible by all requests. The bad thing is this kind of code can pass unit tests and integration tests without any warnings.

A document is good for this issue, but it's not enough; it's hard to guarantee every developer have read that piece of ducument carefully.

Issue Links

• duplicates: TAP5-206 Document that you should not instantiate an @Persist field in its declaration