[
https://issues.apache.org/jira/browse/OAK-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig resolved OAK-617.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.7
Assignee: Michael Dürig
Fixed at revision 1444037
> Generalise Tree.Status.REMOVED to DISCONNECTED
> ----------------------------------------------
>
> Key: OAK-617
> URL: https://issues.apache.org/jira/browse/OAK-617
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Fix For: 0.7
>
>
> I'd like to generalise the {{REMOVED}} status to {{DISCONNECTED}}. Where
> {{REMOVED}} only covers the case where a tree has been removed from its
> parent. The {{DISCONNECTED}} status would in addition cover the case where a
> tree has been disconnected from its parent by other means (i.e. cause by a
> refresh operation).
> Rational:
> All callers of {{Tree.getStatus()}} already interpret the {{REMOVED}} status
> as if it had above semantics of {{DISCONNECTED}} and get confused about the
> {{IllegalArgumentException}} being thrown for the case a node is not removed
> but otherwise disconnected. This is btw. also the root cause for the
> observation made in OAK-606.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
