You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2016/02/16 18:43:18 UTC

[jira] [Commented] (DIRAPI-266) ResultCodeEnum 'NO_SUCH_OBJECT' should have message 'noSuchObject'

    [ https://issues.apache.org/jira/browse/DIRAPI-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148971#comment-15148971 ] 

Emmanuel Lecharny commented on DIRAPI-266:
------------------------------------------

Good catch !

I have *no idea* why we used {{NO_SUCH_OBJECT}} for this error only... This has been introduced back in 2010. A typo most certainly.

> ResultCodeEnum 'NO_SUCH_OBJECT' should have message 'noSuchObject'
> ------------------------------------------------------------------
>
>                 Key: DIRAPI-266
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-266
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 1.0.0-M33
>            Reporter: Claudia S
>            Priority: Minor
>             Fix For: 1.0.0-M34
>
>
> According to [RFC2251|https://www.ietf.org/rfc/rfc2251.txt]  the result code for error 32 is 'noSuchObject'.
> {{org.apache.directory.api.ldap.model.message.ResultCodeEnum}} currently defines:
> {{NO_SUCH_OBJECT(32, "NO_SUCH_OBJECT")}}
> instead of:
> {{NO_SUCH_OBJECT(32, "noSuchObject")}}
> I'm using DSMLv2 and JaxB and the issue I face is when receiving this error the result code cannot be unmarshalled into the corresponding Java enum type {{LDAPResultCode}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)