
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Blocker
|
|
|
|
This issue is blocked by:
|
|
DIRSERVER-236
Modify attribute fails with exception javax.naming.Directory.InvalidAttributeIdentifierException
|
|
|
|
|
|
|
| Resolution Date: |
30/Jan/06 08:34 AM
|
|
This is related to DIRLDAP-84. We had a discussion about it on the mailing list and I want to be sure it is filed in JIRA. Therefore I open a separate issue.
The following entry can be created (note that attribute "voice" does not exist in the schema).
dn: cn=Kate Bush,dc=example,dc=com
cn: Kate Bush
objectclass: top
objectclass: person
sn: Bush
voice: unbelievable
The following operation does neither throw an error nor an exception on
server side
$ ldapadd -p 10389 -D uid=admin,ou=system -w ***** -f addKate.ldif
adding new entry cn=Kate Bush,dc=example,dc=com
But searching Kate causes exceptions on the server (not visible to the
client) like
javax.naming.NamingException: OID for name 'voice' was not found within the
OID
registry
at
org.apache.ldap.server.schema.GlobalOidRegistry.getOid(GlobalOidRegistry.java:176)
at
org.apache.ldap.server.schema.GlobalAttributeTypeRegistry.lookup(GlobalAttributeTypeRegistry.java:124)
at
org.apache.ldap.server.partition.impl.btree.BTreeSearchResultEnumeration.next(BTreeSearchResultEnumeration.java:181)
at
org.apache.ldap.server.enumeration.SearchResultFilteringEnumeration.prefetch(SearchResultFilteringEnumeration.java:299)
at
org.apache.ldap.server.enumeration.SearchResultFilteringEnumeration.<init>(SearchResultFilteringEnumeration.java:110)
at
org.apache.ldap.server.collective.CollectiveAttributeService.search(CollectiveAttributeService.java:279)
at
org.apache.ldap.server.interceptor.InterceptorChain$Entry$1.search(InterceptorChain.java:1178)
at
org.apache.ldap.server.operational.OperationalAttributeService.search(OperationalAttributeService.java:255)
and it is not possible to change the entry afterwards (DIRLDAP-84).
|
|
Description
|
This is related to DIRLDAP-84. We had a discussion about it on the mailing list and I want to be sure it is filed in JIRA. Therefore I open a separate issue.
The following entry can be created (note that attribute "voice" does not exist in the schema).
dn: cn=Kate Bush,dc=example,dc=com
cn: Kate Bush
objectclass: top
objectclass: person
sn: Bush
voice: unbelievable
The following operation does neither throw an error nor an exception on
server side
$ ldapadd -p 10389 -D uid=admin,ou=system -w ***** -f addKate.ldif
adding new entry cn=Kate Bush,dc=example,dc=com
But searching Kate causes exceptions on the server (not visible to the
client) like
javax.naming.NamingException: OID for name 'voice' was not found within the
OID
registry
at
org.apache.ldap.server.schema.GlobalOidRegistry.getOid(GlobalOidRegistry.java:176)
at
org.apache.ldap.server.schema.GlobalAttributeTypeRegistry.lookup(GlobalAttributeTypeRegistry.java:124)
at
org.apache.ldap.server.partition.impl.btree.BTreeSearchResultEnumeration.next(BTreeSearchResultEnumeration.java:181)
at
org.apache.ldap.server.enumeration.SearchResultFilteringEnumeration.prefetch(SearchResultFilteringEnumeration.java:299)
at
org.apache.ldap.server.enumeration.SearchResultFilteringEnumeration.<init>(SearchResultFilteringEnumeration.java:110)
at
org.apache.ldap.server.collective.CollectiveAttributeService.search(CollectiveAttributeService.java:279)
at
org.apache.ldap.server.interceptor.InterceptorChain$Entry$1.search(InterceptorChain.java:1178)
at
org.apache.ldap.server.operational.OperationalAttributeService.search(OperationalAttributeService.java:255)
and it is not possible to change the entry afterwards (DIRLDAP-84).
|
Show » |
| No work has yet been logged on this issue.
|
|