directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <directory-...@incubator.apache.org>
Subject [jira] Resolved: (DIREVE-285) NamingEvent.OBJECT_CHANGED has identical bindings for the old binding and the new binding.
Date Tue, 25 Oct 2005 17:38:55 GMT
     [ http://issues.apache.org/jira/browse/DIREVE-285?page=all ]
     
Alex Karasulu resolved DIREVE-285:
----------------------------------

    Resolution: Fixed

Made sure to have before and after binding be different.  Also packaged ModificationItem[]
into the info object of the event when the event is of the OBJECT_CHANGED type.  Committed
changes in revision 328432 here:

http://svn.apache.org/viewcvs.cgi?view=rev&rev=328432

Built and deployed changes to remote repo for 0.9.3 snapshots.

> NamingEvent.OBJECT_CHANGED has identical bindings for the old binding and the new binding.
> ------------------------------------------------------------------------------------------
>
>          Key: DIREVE-285
>          URL: http://issues.apache.org/jira/browse/DIREVE-285
>      Project: Directory Server
>         Type: Bug
>   Components: jndi-provider
>     Reporter: Enrique Rodriguez
>     Assignee: Alex Karasulu
>      Fix For: 0.9.3

>
> When using an ObjectChangeListener, the generated NamingEvent.OBJECT_CHANGED has identical
bindings for the evt.getNewBinding() and evt.getOldBinding().  This prevents diffs for the
specific attribute(s) that changed.
> ... As evidenced by the following log statement:
> log.debug( id + " >>> object changed: " + evt.getNewBinding() + " from " + evt.getOldBinding()
);
> ... And the following log entry.  What actually changed was the ipPort in the backing
store via LDAP:
> 2482963 [IoThreadPool-7] DEBUG org.apache.configuration.store.EventDirContextListener
 - Listener-1130220104408 >>> object changed: (not relative)cn=org.apache.dns.2,cn=dns,ou=services,ou=configuration,ou=system:
org.apache.ldap.common.message.LockableAttributesImpl:objectClass: apacheServiceConfiguration
> objectClass: extensibleObject
> creatorsName: uid=admin,ou=system
> cn: org.apache.dns.2
> modifiersName: uid=admin,ou=system
> apacheServicePid: org.apache.dns.2
> baseDn: dc=apache,dc=org
> apacheServiceFactoryPid: org.apache.dns.factory
> ipPort: 10053
> createTimestamp: 20051025045832Z
> ipAddress:  10.0.0.1
> modifyTimestamp: 20051025060729Z
>  from (not relative)cn=org.apache.dns.2,cn=dns,ou=services,ou=configuration,ou=system:
org.apache.ldap.common.message.LockableAttributesImpl:objectClass: apacheServiceConfiguration
> objectClass: extensibleObject
> creatorsName: uid=admin,ou=system
> cn: org.apache.dns.2
> modifiersName: uid=admin,ou=system
> apacheServicePid: org.apache.dns.2
> baseDn: dc=apache,dc=org
> apacheServiceFactoryPid: org.apache.dns.factory
> ipPort: 10053
> createTimestamp: 20051025045832Z
> ipAddress:  10.0.0.1
> modifyTimestamp: 20051025060729Z

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message