Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <3768899.317251281656178419.JavaMail.jira@thor>
Date: Thu, 12 Aug 2010 19:36:18 -0400 (EDT)
From: =?utf-8?Q?Michael_D=C3=BCrig_=28JIRA=29?= <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-2714) Selective disabling of checks in
 ItemValidator
In-Reply-To: <25525002.317231281656177944.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/JCR-2714?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael D=C3=BCrig updated JCR-2714:
-------------------------------

    Attachment: JCR-2714.patch

Aforementioned patch

> Selective disabling of checks in ItemValidator
> ----------------------------------------------
>
>                 Key: JCR-2714
>                 URL: https://issues.apache.org/jira/browse/JCR-2714
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>    Affects Versions: 2.2.0
>            Reporter: Michael D=C3=BCrig
>            Assignee: Michael D=C3=BCrig
>         Attachments: JCR-2714.patch
>
>
> I would like to be able to selectively disable checks in ItemValidator in=
 the scope of an operation performed through methods of the SessionState cl=
ass. Doing so would provide simple means for internally modifying (for exam=
ple) protected items. Currently such modifications must be done 'manually' =
on the item state level. This approach is very error prone and not very DRY=
.
> With my upcoming patch in place, setting a protected property would look =
like this:
> final Node parent =3D ...
> final Value value =3D ...
> SessionState sessionState =3D sessionContext.getSessionState();
> Property property =3D sessionState.performUnchecked(new SessionOperation<=
Property>() {
>     public Property perform(SessionContext context) throws RepositoryExce=
ption {
>         return parent.setProperty("foo", value);
>     }
> }, ItemValidator.CHECK_CONSTRAINTS);
> That is, users need to have access to the session context in order to dis=
able checks which makes this only usable from inside Jackrabbit.=20

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.