[
https://issues.apache.org/jira/browse/ZEST-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin resolved ZEST-139.
------------------------------
Resolution: Won't Fix
The thing is, dangling UoWs can be associated with several threads, not only
the one doing the passivation.
To implement this properly we would need to keep all active UoW in some
{{ConcurrentHashMap<Thread,UoW>}} or something so we could iterate on them.
Sounds like an unfortunate and noticeable change for not so much value.
I'm closing this as {{Won't Fix}}, feel free to reopen if you want to discuss.
> Discard dangling UnitOfWorks on passivation
> -------------------------------------------
>
> Key: ZEST-139
> URL: https://issues.apache.org/jira/browse/ZEST-139
> Project: Zest
> Issue Type: Improvement
> Reporter: Paul Merlin
> Fix For: 3.0
>
>
> See http://zest.markmail.org/thread/s3gmlwggeq7vypfp
> If any dangling UoW warn the user with a reasonable error message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
