directory-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tanja Ertl" <>
Subject RE: Transaction for interceptor
Date Wed, 09 Jul 2008 13:05:47 GMT

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,


 -----Original Message-----
From: Emmanuel Lecharny [] On Behalf Of Emmanuel Lecharny
Sent: Wednesday, July 09, 2008 2:34 PM
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├ęcharny

View raw message