Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Date: Thu, 14 Jun 2012 15:28:42 +0000 (UTC)
From: =?utf-8?Q?Michael_D=C3=BCrig_=28JIRA=29?= <jira@apache.org>
To: oak-dev@jackrabbit.apache.org
Message-ID: <932925974.16012.1339687722676.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <2146269035.15923.1339686282560.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (OAK-141) issues related to Node.refresh() as
 opposed to Session.refresh()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/OAK-141?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:all-tabpanel ]

Michael D=C3=BCrig updated OAK-141:
------------------------------

    Component/s:     (was: core)
    Description:=20
(This issue is opened for tracking purposes.)

JSR-283 deprecates Node.refresh(). OAK-JCR implements it by delegating to s=
ession.refresh().

The TCK has a few test cases that rely on the JSR-170/283 semantics.

       Priority: Minor  (was: Major)
       Assignee:     (was: Michael D=C3=BCrig)
     Issue Type: Task  (was: Bug)
        Summary: issues related to Node.refresh() as opposed to Session.ref=
resh()  (was: Calling Node.refresh() on deleted node should throw InvalidIt=
emStateException)
   =20
> 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=C3=BCrig
>            Priority: Minor
>
> (This issue is opened for tracking purposes.)
> JSR-283 deprecates Node.refresh(). OAK-JCR implements it by delegating to=
 session.refresh().
> The TCK has a few test cases that rely on the JSR-170/283 semantics.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira