Apache Directory Project - [jira] Updated: (DIREVE-285) NamingEvent.OBJECT_CHANGED has identical bindings for the

This is Interesting: Free IT Magazines  
Home > Archive > Apache Directory Project > October 2005 > [jira] Updated: (DIREVE-285) NamingEvent.OBJECT_CHANGED has identical bindings for the





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author [jira] Updated: (DIREVE-285) NamingEvent.OBJECT_CHANGED has identical bindings for the
Alex Karasulu (JIRA)

2005-10-25, 5:45 pm

[ http://issues.apache.org/jira/brows...VE-285?page=all ]

Alex Karasulu updated DIREVE-285:
---------------------------------

Fix Version: 0.9.3

Let's take care of this right away.

> 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.LockableA

ttributesImpl: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/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com