You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2015/03/06 12:27:38 UTC

[jira] [Resolved] (OAK-672) Avoid JCR APIs calling other JCR APIs

     [ https://issues.apache.org/jira/browse/OAK-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dürig resolved OAK-672.
-------------------------------
    Resolution: Fixed

Resolving as fixed as most has been done. Let's open specific issues once they come up.

> Avoid JCR APIs calling other JCR APIs
> -------------------------------------
>
>                 Key: OAK-672
>                 URL: https://issues.apache.org/jira/browse/OAK-672
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: jcr
>            Reporter: Michael Dürig
>             Fix For: 1.2
>
>
> As discussed [on the list | http://markmail.org/message/avqtnfamdp56jsqy] we should avoid implementing JCR methods in terms of other JCR methods but rather factor the commonalities out into a common method of the respective delegate. 
> JCR methods calling each other is problematic since it duplicates pre condition checks and makes it considerable more difficult to guarantee certain invariants during the course of the method call (see the discussion wrt. refresh earlier in above thread). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)