[
https://issues.apache.org/jira/browse/DIRAPI-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRAPI-349.
--------------------------------------
Resolution: Fixed
Fixed with commits {{f7529b6685226d35b668804a5c999b1f42c19cb9}} and
{{49621f53be1b3cf2f5777c575a389c451ca6045d}}
> DN with hex values aren't parsed properly when not schema aware
> ---------------------------------------------------------------
>
> Key: DIRAPI-349
> URL: https://issues.apache.org/jira/browse/DIRAPI-349
> Project: Directory Client API
> Issue Type: Bug
> Affects Versions: 2.0.0.AM4
> Reporter: Emmanuel Lecharny
> Priority: Major
> Fix For: 2.0.0.AM5
>
>
> If we create a DN like {{uid = #4869}}, it's properly handled when it's
> schema aware. However, doing the same thing without a {{SchemaManager}} meads
> to some wrong normalized name to be generated :
> {code:java}
> Dn dn = new Dn( "uid = #4869" );
> assertEquals( "uid=Hi", dn.getNormName() );
> {code}
> fails, the {{dn.getNormName()}} calls returns {{uid=}}, with no value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
