1 Reply Latest reply on Dec 12, 2006 9:18 PM by Oliver Yang

    Deploy ejb failed

    Oliver Yang Newbie

      I just installed Jboss4.0.5 with no error. When I deployed my application ejb, it failed. The application ejb runs well on my previous server and they are EJB2.0. I compiled it with the late javeEE lib and unchange the ejb-jar.xml. They are all session beans. When I depolyed them, Jboss gave me the following error:
      14:52:04,026 WARN [verifier] EJB spec violation:
      Bean : SYS/User
      Method : public abstract MutableUser addMobileTagUser(MutableTagUser, int, boolean) throws CodeException, RemoteException
      Section: 7.10.5
      Warning: The methods defined in the remote interface must have a matching method in the bean's class with the same name and same number and types of arguments.

      14:52:04,208 ERROR [MainDeployer] Could not create deployment: file:/home/oyang/jboss-4.0.5.GA/server/default/deploy/ejb.jar
      org.jboss.deployment.DeploymentException: Verification of Enterprise Beans failed, see above for error messages.
      at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:610)
      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:585)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      ............

      Please help.

      Thanks

        • 1. Re: Deploy ejb failed
          Oliver Yang Newbie

          I found it. Exactly the bean metthod is not same as the remote metthod.

          MutableUser addMobileTagUser(MutableTagUser, int, boolean) throws CodeExceptiont


          is not same as bean method. In bean class, it used MutableTagUser super class instead of MutableTagUser. But there was no error when we deployed our application in a old ejb container.

          Is it a bug with the old container?

          Thanks.