[
https://issues.apache.org/jira/browse/DIRSERVER-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSERVER-1652.
------------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0-M3
Assignee: Emmanuel Lecharny
Fixed with http://svn.apache.org/viewvc?rev=1164212&view=rev
You are perfectly right. We get bacj the entry directly from the backend,
without any filtering, thus the attributes are named using their OID, not their
name. I have modified the proposed patch by requiring all the user and
operational attributes, which is faster, and the entry.get(
SchemaConstants.CONTEXT_CSN_AT ) calls correctly get back the EntryCSN
attribute's value.
Thanls for the JIRA !
> filtering attributes against oid and not against the name
> ---------------------------------------------------------
>
> Key: DIRSERVER-1652
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1652
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: 2.0.0-M2
> Reporter: Hajo Kliemeck
> Assignee: Emmanuel Lecharny
> Priority: Minor
> Fix For: 2.0.0-M3
>
> Attachments: DefaultDirectoryService.diff
>
>
> on the DefaultDirectoryService startup the service has to get the last CSN.
> Therefore it will make a lookup request to get the attribute. The Jdbm
> partition, which is queried, will filter all attributes which are not
> requested. The filtering will filter against the OID and not against the name
> of the attribute.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
