You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org> on 2012/04/27 17:34:50 UTC
[jira] [Created] (DIRSERVER-1718) Problems when adding a schema
containing one or more uppercased letters
Pierre-Arnaud Marcelot created DIRSERVER-1718:
-------------------------------------------------
Summary: Problems when adding a schema containing one or more uppercased letters
Key: DIRSERVER-1718
URL: https://issues.apache.org/jira/browse/DIRSERVER-1718
Project: Directory ApacheDS
Issue Type: Bug
Affects Versions: 2.0.0-M6
Reporter: Pierre-Arnaud Marcelot
Priority: Blocker
Fix For: 2.0.0-M7
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).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSERVER-1718) Problems when adding a schema
containing one or more uppercased letters
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466504#comment-13466504 ]
Emmanuel Lecharny commented on DIRSERVER-1718:
----------------------------------------------
There were a NPE while trying to remove the content of the schema, which was empty.
> Problems when adding a schema containing one or more uppercased letters
> -----------------------------------------------------------------------
>
> Key: DIRSERVER-1718
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1718
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 2.0.0-M6
> Reporter: Pierre-Arnaud Marcelot
> Priority: Blocker
> Fix For: 2.0.0-M7
>
>
> 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).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DIRSERVER-1718) Problems when adding a schema
containing one or more uppercased letters
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRSERVER-1718.
------------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0-M8
Fixed with http://svn.apache.org/viewvc?rev=1392051&view=rev
Test in http://svn.apache.org/viewvc?rev=1392053&view=rev
> Problems when adding a schema containing one or more uppercased letters
> -----------------------------------------------------------------------
>
> Key: DIRSERVER-1718
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1718
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 2.0.0-M6
> Reporter: Pierre-Arnaud Marcelot
> Priority: Blocker
> Fix For: 2.0.0-M8, 2.0.0-M7
>
>
> 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).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira