[DIRSERVER-1718] Problems when adding a schema containing one or more uppercased letters

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.0.0-M6
• Fix Version/s: 2.0.0-M7, 2.0.0-M8
• Assignee: Unassigned
• Reporter: Pierre-Arnaud Marcelot
• Created: 27/Apr/12 15:32
• Updated: 30/Sep/12 15:54
• Resolved: 30/Sep/12 15:54

Description

We've had some problems to sometimes add (in previous versions) and delete (still present) schemas containing one or more uppercased letters.

If the schema is inserted with an all lowercased name, everything works fine.

As an example, here's what happens when I try to remove a schema containing uppercased letters:
!STACK 0
java.lang.Exception: [LDAP: error code 80 - OTHER: failed for MessageType : DEL_REQUEST
Message ID : 41
Del request
Entry : 'cn=schemaTAS2,ou=schema'
org.apache.directory.shared.ldap.model.message.DeleteRequestImpl@5cd0e8d7: null]
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkResponse(DirectoryApiConnectionWrapper.java:1279)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.access$9(DirectoryApiConnectionWrapper.java:1247)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper$7.run(DirectoryApiConnectionWrapper.java:995)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.runAndMonitor(DirectoryApiConnectionWrapper.java:1174)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkConnectionAndRunAndMonitor(DirectoryApiConnectionWrapper.java:1108)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.deleteEntry(DirectoryApiConnectionWrapper.java:1017)
at org.apache.directory.studio.ldapbrowser.core.jobs.DeleteEntriesRunnable.deleteEntry(DeleteEntriesRunnable.java:382)
at org.apache.directory.studio.ldapbrowser.core.jobs.DeleteEntriesRunnable.optimisticDeleteEntryRecursive(DeleteEntriesRunnable.java:272)
at org.apache.directory.studio.ldapbrowser.core.jobs.DeleteEntriesRunnable.run(DeleteEntriesRunnable.java:173)
at org.apache.directory.studio.connection.core.jobs.StudioConnectionJob.run(StudioConnectionJob.java:109)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

I suspect a problem in the way we process the names of the schema (lowercasing it and using that a reference maybe).