You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Enrique Rodriguez (JIRA)" <di...@incubator.apache.org> on 2005/10/25 09:02:55 UTC
[jira] Created: (DIREVE-285) NamingEvent.OBJECT_CHANGED has identical bindings for the old binding and the new binding.
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
Assigned to: Alex Karasulu
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
[jira] Closed: (DIRSERVER-349) NamingEvent.OBJECT_CHANGED has
identical bindings for the old binding and the new binding.
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny closed DIRSERVER-349.
---------------------------------------
closed
> NamingEvent.OBJECT_CHANGED has identical bindings for the old binding and the new binding.
> ------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-349
> URL: https://issues.apache.org/jira/browse/DIRSERVER-349
> Project: Directory ApacheDS
> Issue Type: Bug
> Reporter: Enrique Rodriguez
> Assignee: Alex Karasulu
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIREVE-285) NamingEvent.OBJECT_CHANGED has identical bindings for the old binding and the new binding.
Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
[ 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
[jira] Updated: (DIREVE-285) NamingEvent.OBJECT_CHANGED has identical bindings for the old binding and the new binding.
Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-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.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