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 "Jukka Zitting (JIRA)" <ji...@apache.org> on 2013/09/17 17:08:51 UTC
[jira] [Commented] (OAK-141) issues related to Node.refresh() as
opposed to Session.refresh()
[ https://issues.apache.org/jira/browse/OAK-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13769588#comment-13769588 ]
Jukka Zitting commented on OAK-141:
-----------------------------------
I adjusted the Item.refresh() implementation slightly in revision 1524089 (to fix a TCK failure), and adjusted the logged warning to better reflect the fact that the current implementation isn't strictly spec-compliant.
> issues related to Node.refresh() as opposed to Session.refresh()
> ----------------------------------------------------------------
>
> Key: OAK-141
> URL: https://issues.apache.org/jira/browse/OAK-141
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: jcr
> Reporter: Michael Dürig
> Priority: Minor
>
> (This issue is opened for tracking purposes.)
> JSR-333 deprecates Node.refresh() [1]. OAK-JCR implements it by delegating to session.refresh().
> The TCK has a few test cases that rely on the JSR-170/283 semantics.
> [1] http://java.net/jira/browse/JSR_333-42
--
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