0 Replies Latest reply on Oct 20, 2003 9:21 AM by dalager

    Possible aop/remoting bug in DR3?

    dalager

      When I access methods on AOP-remoting-advised Pojos I get a strange IllegalArgumentException on the server when calling methods with arguments (see stacktrace below)

      Methods with no arguments work fine.

      Could this be a bug?

      Sincerely
      Christian

      Stacktrace:

      java.lang.IllegalArgumentException: wrong number of arguments
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.aop.ClassAdvisor$MethodTailInterceptor.invoke(ClassAdvisor.java:892)
      at org.jboss.aop.Invocation.invokeNext(Invocation.java:83)
      at org.jboss.aop.ClassAdvisor.dynamicInvoke(ClassAdvisor.java:803)
      at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:87)
      at org.jboss.aop.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:75)
      at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:326)
      at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:250)
      at org.jboss.remoting.transport.socket.SocketServerInvoker$Client.run(SocketServerInvoker.java:208)