You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Benedikt Ritter (Updated) (JIRA)" <ji...@apache.org> on 2012/02/26 22:52:48 UTC
[jira] [Updated] (SANDBOX-399) [BeanUtils2] Handle methods that
return void separatly
[ https://issues.apache.org/jira/browse/SANDBOX-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benedikt Ritter updated SANDBOX-399:
------------------------------------
Attachment: SANDBOX-399.txt
I've implemented {{NullBeanAccessor}} as a special case implementation of the {{BeanAccessor}} interface, that will be used by {{DefaultArgumentsAccessor}} when ever a method is invoked that returns void or if the invocation of a method returns null.
> [BeanUtils2] Handle methods that return void separatly
> ------------------------------------------------------
>
> Key: SANDBOX-399
> URL: https://issues.apache.org/jira/browse/SANDBOX-399
> Project: Commons Sandbox
> Issue Type: Improvement
> Components: BeanUtils2
> Affects Versions: Nightly Builds
> Reporter: Benedikt Ritter
> Attachments: SANDBOX-399.txt
>
>
> Since {{ArgumentsAccessor.withArguments(...)}} returns a new {{BeanAccessor}} problems occur if a method's return type is void. To deal with this a Special Case implementation of BeanAccessor should be invented.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira