You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@directory.apache.org by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org> on 2011/05/05 09:44:03 UTC

[jira] [Updated] (DIRSHARED-118) Method AbstractMessage.setMessageId(...) should have a return type set to type of message in order to allow chaining like the other setter methods

     [ https://issues.apache.org/jira/browse/DIRSHARED-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre-Arnaud Marcelot updated DIRSHARED-118:
---------------------------------------------

    Fix Version/s:     (was: 1.0.0-M3)
                   1.0.0-M4

> Method AbstractMessage.setMessageId(...) should have a return type set to type of message in order to allow chaining like the other setter methods
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DIRSHARED-118
>                 URL: https://issues.apache.org/jira/browse/DIRSHARED-118
>             Project: Directory Shared
>          Issue Type: Bug
>    Affects Versions: 1.0.0-M2
>            Reporter: Pierre-Arnaud Marcelot
>            Priority: Minor
>             Fix For: 1.0.0-M4
>
>
> Method AbstractMessage.setMessageId(...) should have a return type set to type of message in order to allow chaining like the other setter methods.
> For example, I'd like to be able to this:
>         BindRequest bindRequest = new BindRequest();
>         bindRequest.setMessageId( ... ).setName( ... ).setCredentials( ... ) ... etc

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira