[jboss-user] [JBoss AOP] - Re: bug or feature? methodInvocation.getArguments() empty ar

[DerMas]

"flavia.rainone at jboss.com" wrote : It is a consistency bug that has been fixed, actually.
  | 
  | In the previous version, that method would result in null on one cenario and in an empty array on a different weaving mode.
  | 
  | Now, we got rid of this inconsistency by making it always return an non-null array. This has also been formalized by javadoc documentation:
  | 
  | http://www.jboss.org/jbossaop/docs/2.0.0.GA/docs/aspect-framework/apidocs/org/jboss/aop/joinpoint/MethodInvocation.html#getArguments()
  | 
  | With that documentation, you are now assured that it will always return a non-null array and this won't change again, it is part of the JBoss AOP API spec.

Ok, thx for your answer =)

Now I just need to get rid of the sysouts like:


  | [aop-debug] org.jboss.remoting.transport.socket.MicroSocketClientInvoker SocketClientInvoker[10eeb26, socket://127.0.0.1:3873] disconnecting ...
  | [aop-trace] org.jboss.remoting.MicroRemoteClientInvoker SocketClientInvoker[10eeb26, socket://127.0.0.1:3873] disconnecting ...
  | 

when running my ejb in jboss as 4.2.2 and everything would be fine again :)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191147#4191147

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191147