You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stefan Seelmann (JIRA)" <ji...@apache.org> on 2009/08/06 17:09:14 UTC

[jira] Commented: (DIRSERVER-1396) How to extend org.apache.directory.server.core.operational.OperationalAttributeInterceptor , so that I can customize it

    [ https://issues.apache.org/jira/browse/DIRSERVER-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740099#action_12740099 ] 

Stefan Seelmann commented on DIRSERVER-1396:
--------------------------------------------

Just for the record: Instead of using '+' (this would request all operational attributes) it is also possibe to reqeust the required attribute by their names (e.g. createTimestamp, modifyTimestamp, etc.). IMO the client must be fixed. All other LDAP server have the same behaviour and don't return operational attributes unless requested.

Anyway, you could try to modify lookup(), list() and search() methods and add your needed operational attributes to the opContext.


> How to extend org.apache.directory.server.core.operational.OperationalAttributeInterceptor , so that I can customize it
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1396
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1396
>             Project: Directory ApacheDS
>          Issue Type: Wish
>         Environment: windows
>            Reporter: satish
>
> How to extend Operational Attribute Interceptor, so that I can customize it to my requirement
> My requirement is,
> I am using IBM websphere PUMA as client to query ApacheDS,
> At this point I am unable to fetch operational attributes, and requested ApacheDS if any setting can be made, you check the description in this link
> https://issues.apache.org/jira/browse/DIRSERVER-1392 
> IBM Puma team says 
> "ApacheSD is not a supported LDAP vendor. A requirement to put + in front of operational attributes would not be a simple modification to VMM, but would rather need to be handled as an enhancement."
> I am planning to extend org.apache.directory.server.core.operational.OperationalAttributeInterceptor with my custom class to return operational attributes,
> any help in this regard is appreciated.
> Thank you.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.