java.lang.IllegalArgumentException

Invalid ejb jar [myejb.jar]: it > contains zero ejb. > > Note: > > 1. A valid ejb jar requires at least one session, entity (1.x/2.x > style), or > message-driven bean. > > 2. EJB3+ entity beans (@Entity) are POJOs and please package them as > library > jar. > > 3. If the jar file contains valid EJBs which are annotated with EJB > component > level annotations (@Stateless, @Stateful, @MessageDriven, @Singleton), > please > check server.log to see whether the annotations were processed properly. > > at > com.sun.enterprise.deployment.util.EjbBundleValidator.accept(EjbBundleValidator.java:76) > > > at > com.sun.enterprise.deployment.util.ApplicationValidator.accept(ApplicationValidator.java:128) > > > at > com.sun.enterprise.deployment.EjbBundleDescriptor.visit(EjbBundleDescriptor.java:730) > > >

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web25450

  • via Oracle Community by kikujiro, 11 months ago
    Invalid ejb jar [myejb.jar]: it > contains zero ejb. > > Note: > > 1. A valid ejb jar requires at least one session, entity (1.x/2.x > style), or > message-driven bean. > > 2. EJB3+ entity beans (@Entity) are POJOs and please package them as
  • via Oracle Community by ljnelson, 11 months ago
    Invalid ejb jar [ngp-constituent-ejb-1.0-SNAPSHOT.jar]: it contains zero ejb. Note: 1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message-driven bean. 2. EJB3+ entity beans (@Entity) are POJOs and please package them
  • Invalid ejb jar [wpof-ejb-timer]: it contains zero ejb. Note: 1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message-driven bean. 2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar. 3
  • Stack trace

    • java.lang.IllegalArgumentException: Invalid ejb jar [myejb.jar]: it > contains zero ejb. > > Note: > > 1. A valid ejb jar requires at least one session, entity (1.x/2.x > style), or > message-driven bean. > > 2. EJB3+ entity beans (@Entity) are POJOs and please package them as > library > jar. > > 3. If the jar file contains valid EJBs which are annotated with EJB > component > level annotations (@Stateless, @Stateful, @MessageDriven, @Singleton), > please > check server.log to see whether the annotations were processed properly. > > at > com.sun.enterprise.deployment.util.EjbBundleValidator.accept(EjbBundleValidator.java:76) > > > at > com.sun.enterprise.deployment.util.ApplicationValidator.accept(ApplicationValidator.java:128) > > > at > com.sun.enterprise.deployment.EjbBundleDescriptor.visit(EjbBundleDescriptor.java:730) > > > at com.sun.enterprise.deployment.Application.visit(Application.java:1765)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.