[
https://issues.apache.org/jira/browse/BEANUTILS-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575318#action_12575318
]
Niall Pemberton commented on BEANUTILS-309:
-------------------------------------------
The problem is it uses the type (class) of the parameters to find the
appropriate constructor to invoke - so for example if you had something like
the following
public class Foo {
public Foo(String param) {
}
public Foo(Integer param) {
}
}
And called
ConstructorUtils.invokeConstructor(Foo.class, new Object[] {null});
Which constructor should it use? I guess it could just pick one arbitarily, but
it might still cause problems.
It will probably be a while before I get round to looking at this, but if you
provide a patch with test cases then it will move up on my list
> Passing a null argument to ConstructorUtils.invokeConstructor causes
> NullPointerException
> -----------------------------------------------------------------------------------------
>
> Key: BEANUTILS-309
> URL: https://issues.apache.org/jira/browse/BEANUTILS-309
> Project: Commons BeanUtils
> Issue Type: Bug
> Affects Versions: 1.7.0, 1.8.0-BETA
> Reporter: Xavier Poinsard
>
> I am invoking ConstructorUtils.invokeConstructor with an array of arguments
> and one of these arguments is null.
> This causes a NullPointerException line 120 in Class ConstructorUtils.
> Since its not forbidden to pass null argument to a constructor,
> ConstructorUtils should handle it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
