While I was working on JBAOP-379, I found out that call arguments array have never been
null for empty arguments list. This means that CallInvocation.getArguments returns an
empty array in that case.
So, changing this would be equivalent to changing method and constructor execution
arguments to being empty instead of null. We would be changing the semantics of the
getArguments method anyway.
On the other hand, we would prefer to be more consistent and stick with only one of the
possibilities:
- null arguments array when there are no arguments
- empty arguments array when there are no arguments
Given that, I want to know how do you find the idea of keeping 2.0 as is (i.e., all
arguments array are non-null).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032145#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...