com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [ldap-1.0.1-SNAPSHOT] -- Invalid ejb jar [/opt/company/glassfish/domains/domain1/applications/j2ee-modules/ldap-1.0.1-SNAPSHOT]: 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), please check server.log to see whether the annotations were processed properly.

Oracle Community | samsina | 8 years ago
  1. 0

    glassfish EJB problem

    Oracle Community | 8 years ago | samsina
    com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [ldap-1.0.1-SNAPSHOT] -- Invalid ejb jar [/opt/company/glassfish/domains/domain1/applications/j2ee-modules/ldap-1.0.1-SNAPSHOT]: 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), please check server.log to see whether the annotations were processed properly.
  2. 0

    Referencing error: This bundle has no bean of name | Java.net

    java.net | 1 year ago
    com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [wsc] -- Referencing error: This bundle has no bean of name [UserManager]
  3. 0

    Referencing error: This bundle has no bean of name

    Oracle Community | 5 years ago | mohitkumarjoshi
    com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [wsc] -- Referencing error: This bundle has no bean of name [UserManager]
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    "Contains no EJBs"...but it does, and no server.log errors

    Oracle Community | 6 years ago | ljnelson
    java.lang.IllegalArgumentException: 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 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.
  6. 0

    Include EJB.jar or EJB (project) in other EJB o... | Oracle Community

    oracle.com | 1 year ago
    java.lang.IllegalArgumentException: 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. 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.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.IllegalArgumentException

      Invalid ejb jar [/opt/company/glassfish/domains/domain1/applications/j2ee-modules/ldap-1.0.1-SNAPSHOT]: 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), please check server.log to see whether the annotations were processed properly.

      at com.sun.enterprise.deployment.util.EjbBundleValidator.accept()
    2. Deployment Object Library
      ApplicationArchivist.openArchive
      1. com.sun.enterprise.deployment.util.EjbBundleValidator.accept(EjbBundleValidator.java:95)
      2. com.sun.enterprise.deployment.EjbBundleDescriptor.visit(EjbBundleDescriptor.java:729)
      3. com.sun.enterprise.deployment.archivist.EjbArchivist.validate(EjbArchivist.java:190)
      4. com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:790)
      5. com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:744)
      5 frames
    3. com.sun.enterprise
      Deployer.loadDescriptors
      1. com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:349)
      1 frame