[
https://issues.apache.org/jira/browse/TAP5-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645583#action_12645583
]
Howard M. Lewis Ship commented on TAP5-323:
-------------------------------------------
This is very hard to detect, as is differentiating mutable types from immutable
types.
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
