| Stefan Zoerner (JIRA) 2005-11-13, 5:45 pm |
| [ http://issues.apache.org/jira/brows...VE-307?page=all ]
Stefan Zoerner updated DIREVE-307:
----------------------------------
Comment: was deleted
> ldapmodrdn failed upon encountering blank space
> -----------------------------------------------
>
> Key: DIREVE-307
> URL: http://issues.apache.org/jira/browse/DIREVE-307
> Project: Directory Server
> Type: Bug
> Components: protocol
> Versions: 0.9.3
> Reporter: Endi S. Dewata
> Assignee: Alex Karasulu
>
> When specifying multiple entries for ldapmodrdn operation, according to the manual page (http://linuxcommand.org/man_pages/ldapmodrdn1.html) "one or more blank lines may be used to separate each DN/RDN pair." However, it seems that currently ApacheDS do
es not allow any blank lines in the ldapmodrdn input.
> Note: I'm not sure if at least one blank line is actually required to separate the entires. To be safe, the blank line maybe can be made totally optional.
> The following operation currently will succeed in renaming both entries.
> ou=test,dc=apache,dc=org
> ou=test2
> ou=test2,dc=apache,dc=org
> ou=test
> The following command currently will fail on the second entry:
> ou=test,dc=apache,dc=org
> ou=test2
> ou=test2,dc=apache,dc=org
> ou=test
> Here is the exception:
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> at java.util.ArrayList.RangeCheck(ArrayList.java:507)
> at java.util.ArrayList.remove(ArrayList.java:392)
> at org.apache.ldap.common.name.LdapName.remove(LdapName.java:605)
> at org.apache.ldap.server.protocol.ModifyDnHandler.messageReceived(ModifyDnHandler.java:79)
> at org.apache.mina.protocol.handler.DemuxingProtocolHandler.messageReceived(DemuxingProtocolHandler.java:70)
> at org.apache.mina.protocol.AbstractProtocolFilterChain$2. messageReceived(AbstractProtocolFilterCh
ain.java:149)
> at org.apache.mina.protocol.AbstractProtocolFilterChain. callNextMessageReceived(AbstractProtocol
FilterChain.java:365)
> at org.apache.mina.protocol.AbstractProtocolFilterChain.access$1000(AbstractProtocolFilterChain.java:50)
> at org.apache.mina.protocol.AbstractProtocolFilterChain$Entry$1. messageReceived(AbstractProtocolFilterCh
ain.java:524)
> at org.apache.mina.protocol.AbstractProtocolFilterChain$1. messageReceived(AbstractProtocolFilterCh
ain.java:99)
> at org.apache.mina.protocol.AbstractProtocolFilterChain. callNextMessageReceived(AbstractProtocol
FilterChain.java:365)
> at org.apache.mina.protocol.AbstractProtocolFilterChain. messageReceived(AbstractProtocolFilterCh
ain.java:356)
> at org.apache.mina.protocol.ProtocolSessionManagerFilterChain$1. messageReceived(ProtocolSessionManagerFi
lterChain.java:77)
> at org.apache.mina.protocol.AbstractProtocolFilterChain. callNextMessageReceived(AbstractProtocol
FilterChain.java:365)
> at org.apache.mina.protocol.AbstractProtocolFilterChain.access$1000(AbstractProtocolFilterChain.java:50)
> at org.apache.mina.protocol.AbstractProtocolFilterChain$Entry$1. messageReceived(AbstractProtocolFilterCh
ain.java:524)
> at org.apache.mina.protocol.filter.ProtocolThreadPoolFilter.processEvent(ProtocolThreadPoolFilter.java:108)
> at org.apache.mina.util.BaseThreadPool$Worker.processEvents(BaseThreadPool.java:393)
> at org.apache.mina.util.BaseThreadPool$Worker.run(BaseThreadPool.java:333)
--
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
|