Return-Path: Delivered-To: apmail-directory-users-archive@www.apache.org Received: (qmail 34040 invoked from network); 9 Jul 2008 14:02:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Jul 2008 14:02:35 -0000 Received: (qmail 91676 invoked by uid 500); 9 Jul 2008 14:02:35 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 91652 invoked by uid 500); 9 Jul 2008 14:02:35 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 91640 invoked by uid 99); 9 Jul 2008 14:02:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jul 2008 07:02:35 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [64.211.150.143] (HELO mailgw.avideurope.com) (64.211.150.143) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jul 2008 14:01:43 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Transaction for interceptor Date: Wed, 9 Jul 2008 15:02:03 +0100 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Transaction for interceptor Thread-Index: Acjhy+ag8lTw3ZAOTxKYvvz3G5o0OgAADd7Q From: "Tanja Ertl" To: X-Virus-Checked: Checked by ClamAV on apache.org Hi Alex, does this mean, it is not possible now, but will be in a future release? Or can we do this ourselves using this "back links" right now? Thanks, Tanja -----Original Message----- From: akarasulu@gmail.com [mailto:akarasulu@gmail.com] On Behalf Of Alex = Karasulu Sent: Wednesday, July 09, 2008 3:58 PM To: users@directory.apache.org Subject: Re: Transaction for interceptor This is something we actually planned to implement using back links. = And yes atomicity would be needed and can be achieved. Alex On Wed, Jul 9, 2008 at 9:05 AM, Tanja Ertl wrote: > Hi, > > with transactional I mean that the origin action and the work done in = the > interceptor is an *atomic* piece of work. If one fails, the other = should not > be succeeding, too. Like a transaction in database context. > One of our use cases is that our users need to maintain a memberOf > attribute, where all groups of the user are listed. This should be = tracked > by an interceptor. If you add a user to a group the interceptor should > update the memberOf attribute of the user entry. This should only = happen, if > the original request succeeds. That's no problem, the interceptor = could > start the work after the nexus has executed the request successfully. = But > vice versa, if the interceptor fails to add the group to the memberOf > attribute, the original request should be rolled backed, too. > > Bye, > Tanja > > -----Original Message----- > From: Emmanuel Lecharny [mailto:elecharny@gmail.com] On Behalf Of = Emmanuel > Lecharny > Sent: Wednesday, July 09, 2008 2:34 PM > To: users@directory.apache.org > Subject: Re: Transaction for interceptor > > Tanja Ertl wrote: > > Hi, > > > > > > > > we would like to add our own interceptor to the ApacheDS interceptor > > chain to do some work when new entries are added/deleted,... > > > That's should not be complex. We are around if you have any problem or > questions ! > > Is there a way to make this transactional with the "real action"? > > > Can you define a little bit more what you mean by 'transactional" ? > > It would also help to know which kind of modification you will do in > this added interceptor. > > Thanks ! > > -- > -- > cordialement, regards, > Emmanuel L=E9charny > www.iktek.com > directory.apache.org > > >