[
https://issues.apache.org/jira/browse/DIRSERVER-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983426#action_12983426
]
Emmanuel Lecharny commented on DIRSERVER-1603:
----------------------------------------------
Now that I have implemented the filter, I have many failures. When I look at
one failing test I see this code :
/**
* Test a lookup( DN, "+") operation
*/
@Test
public void testLookupPlus() throws Exception
{
service.setDenormalizeOpAttrsEnabled( true );
Entry entry = connection.lookup( "cn=test,ou=system", "+" );
assertNotNull( entry );
// We should have 5 attributes
assertEquals( 7, entry.size() ); <<<=== An entry is only suppose to
have 4 operational attributes
It seems that we are not interpreting RFC3673 correctly here...
> Doing a lookup requiring an AT which is inherited by some of the entry's AT
> does not return anything
> ----------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1603
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1603
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.7
> Reporter: Emmanuel Lecharny
> Priority: Critical
> Fix For: 2.0-M1
>
>
> If we do a lookup, listing some attributes to get in the returned entry, and
> if we have AT which inherit the given ATs, we don't get anything.
> For instance,
> Entry entry = connection.lookup( "cn=test,ou=system", "name" );
> return an empty entry.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
