[
https://issues.apache.org/jira/browse/DIRSERVER-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632232#action_12632232
]
Emmanuel Lecharny commented on DIRSERVER-840:
---------------------------------------------
The big issue we have is that the ChangeLog interceptor is trying to revert the
modification, and this include modification of operational attributes which
have been added in the second pass.
IMO, we should create a second class of attributes : those who have been added
by the server, w<hich shoul dbypass the Schema Interceptor.
> Double modification on a modify ?
> ---------------------------------
>
> Key: DIRSERVER-840
> URL: https://issues.apache.org/jira/browse/DIRSERVER-840
> Project: Directory ApacheDS
> Issue Type: Improvement
> Affects Versions: 1.5.1
> Reporter: Emmanuel Lecharny
> Assignee: Emmanuel Lecharny
> Fix For: 1.5.5
>
>
> We have had a convo with alex about the OperationalService. I saw that when
> doing a modification on an entry, we first call the next interceptor (and
> this will modify the entry on the backend), then we add two new attributes
> (modifiers name and date) and store again the data into the backend. This
> does not seems to be very efficient, but we don't remember the reason why
> it's done like that ...
> Here is the convo
> elecharny in OperationalService
> akarasulu yep
> elecharny when doing a modify,
> akarasulu ahha
> elecharny you first call the next interceptor, then you update the nexus with
> the entry with
> elecharny two new attributes
> elecharny why don't you add the attrs into the entry and then call the netx
> interceptors ?
> akarasulu hmmm I had some reason for this
> elecharny this is a simple modify instead of two
> akarasulu don't remember
> akarasulu yeah yeah I see what you mean
> akarasulu can't remember now
> elecharny this seems to cost the double
> akarasulu yes it does
> akarasulu can you put this in JIRA
> elecharny yeah
> akarasulu just past this info
> akarasulu from IRC
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
