[
https://issues.apache.org/jira/browse/DIRSERVER-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532022
]
Emmanuel Lecharny commented on DIRSERVER-1080:
----------------------------------------------
I _do_ have a fix for this issue (and even two fixes :), but it leads to
complex impact on the schema interceptor. If possible, we should consider
inverting the operationalAttribute and schema interceptors in the chain. FYI,
there are other place in the code where the op attributes are steup _after_ the
schema interceptor, but I consider this as a hack.
Let's discuss this issue ...
Regarding Stefan comment : yes, we will fix it.
> LDAP modify operation does not create or update necessary operational
> attributes within an entry
> ------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1080
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1080
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: ldap
> Affects Versions: 1.5.1
> Environment: * ApacheDS 1.5.1
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> * Windows XP Professional SP2
> Reporter: Stefan Zoerner
> Assignee: Alex Karasulu
>
> If an existing entry is modified (e.g. additional attribute addition), and
> the operational attributes "modifiersName" and "modifyTimestamp" are not
> present, they are not present afterwards as well.
> I have extended the existing test case
> org.apache.directory.server.core.operational.OperationalAttributeServiceITest
> in order to demonstrate this and to depict the desired behavior (svn commit
> follows).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
