Affects Version/s: 5.0.15
Fix Version/s: 5.0.16
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.
|Affects Version/s||5.0.15 [ 12313429 ]|
|Assignee||Howard M. Lewis Ship [ hlship ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Resolution||Fixed [ 1 ]|
|Status||In Progress [ 3 ]||Closed [ 6 ]|
|Fix Version/s||5.0.16 [ 12313427 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|142d 3h||1||Howard M. Lewis Ship||06/Nov/08 21:44|
|1h 20m||1||Howard M. Lewis Ship||06/Nov/08 23:04|