I know, this issue creeps up every so often in our team.. but quite
rare.. how do you determine a im/mutable object? You mean that you can
only use primitives (null included)? That might be useful, but only if
configurable to enable/disable this "strict" behavior..
Yunhua Sang (JIRA) wrote:
A persistent field with inline mutable object initialization should not be
allowed.
------------------------------------------------------------------------------------
Key: TAP5-323
URL: https://issues.apache.org/jira/browse/TAP5-323
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.0.16
Reporter: Yunhua Sang
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
