directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <directory-...@incubator.apache.org>
Subject [jira] Commented: (DIREVE-281) Attribute from extensibleObject cannot be used in search filter.
Date Sun, 23 Oct 2005 16:59:06 GMT
    [ http://issues.apache.org/jira/browse/DIREVE-281?page=comments#action_12332897 ] 

Alex Karasulu commented on DIREVE-281:
--------------------------------------

The question is whether an AttributeType is expected as you say to determine the matching
semantics based on matchingRules for the attribute.   Meaning how does the directory match
for that attribute if there are no matchingRules associated with it?  I think the attribute
MUST have an attributeType definition supplied in the schema.

extensibleObject just allows us to add any attribute to the entry .. but that attribute must
be defined.  Otherwise according to filter processing rules the clause in the filter must
be ignored.


> Attribute from extensibleObject cannot be used in search filter.
> ----------------------------------------------------------------
>
>          Key: DIREVE-281
>          URL: http://issues.apache.org/jira/browse/DIREVE-281
>      Project: Directory Server
>         Type: Bug
>   Components: jndi-provider
>     Reporter: Enrique Rodriguez
>     Assignee: Alex Karasulu

>
> The following filter fails during DirContext.search() when the attribute used is from
an extensibleObject:
> String filter = "(servicePid=org.apache.dns.factory)";
> LDIF excerpt:
> dn: ou=dns,ou=services,ou=configuration,ou=system
> objectClass: top
> objectClass: organizationalUnit
> objectClass: extensibleObject
> ou: dns
> servicePid: org.apache.dns.factory
> org.apache.ldap.server.interceptor.InterceptorException: Unexpected exception. [Root
exception is java.lang.RuntimeException: OID for name 'servicePid' was not found within the
OID registry]
> 	at org.apache.ldap.server.interceptor.InterceptorChain.throwInterceptorException(InterceptorChain.java:1368)
> 	at org.apache.ldap.server.interceptor.InterceptorChain.search(InterceptorChain.java:754)
> 	at org.apache.ldap.server.partition.DirectoryPartitionNexusProxy.search(DirectoryPartitionNexusProxy.java:371)
> 	at org.apache.ldap.server.partition.DirectoryPartitionNexusProxy.search(DirectoryPartitionNexusProxy.java:359)
> 	at org.apache.ldap.server.jndi.ServerDirContext.search(ServerDirContext.java:616)
> ...
> Caused by: java.lang.RuntimeException: OID for name 'servicePid' was not found within
the OID registry
> 	at org.apache.ldap.server.normalization.ValueNormalizingVisitor.visit(ValueNormalizingVisitor.java:71)
> 	at org.apache.ldap.common.filter.SimpleNode.accept(SimpleNode.java:168)
> 	at org.apache.ldap.common.filter.BranchNode.accept(BranchNode.java:356)
> 	at org.apache.ldap.server.normalization.NormalizationService.search(NormalizationService.java:163)
> 	at org.apache.ldap.server.interceptor.InterceptorChain.search(InterceptorChain.java:746)
> 	... 22 more

-- 
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


Mime
View raw message