1 Reply Latest reply on Apr 27, 2012 1:07 PM by jainmanglesh

    not able to deploy ear with jar and war file on glassfish v3.1.2

    jainmanglesh
      Hi, I am getting following error though i can see ejb classes (with proper annotations in ejb classes) in jar file. [#|2012-04-27T09:49:07.924+0100|SEVERE|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=80;_ThreadName=admin-thread-pool-4854(4);|Invalid ejb jar [myjar.jar]: it co ntains 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 annotati ons were processed properly. java.lang.IllegalArgumentException: Invalid ejb jar [quantum.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 annotati ons 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)         at com.sun.enterprise.deployment.archivist.ApplicationArchivist.validate(ApplicationArchivist.java:830)         at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openWith(ApplicationArchivist.java:277)         at com.sun.enterprise.deployment.archivist.ApplicationFactory.openWith(ApplicationFactory.java:240)         at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:175)         at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:94)         at com.sun.enterprise.v3.server.ApplicationLifecycle.loadDeployer(ApplicationLifecycle.java:827)         at com.sun.enterprise.v3.server.ApplicationLifecycle.setupContainerInfos(ApplicationLifecycle.java:769)         at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:368)         at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)         at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389)         at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348)         at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363)         at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085)         at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95)         at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291)         at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259)         at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:461)         at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:212)         at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)         at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)         at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354)         at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)         at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849)         at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746)         at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045)         at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228)         at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)         at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)         at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)         at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)         at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)         at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)         at com.sun.grizzly.ContextTask.run(ContextTask.java:71)         at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)         at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)         at java.lang.Thread.run(Thread.java:722) |#] [#|2012-04-27T09:49:08.017+0100|SEVERE|glassfish3.1.2|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=80;_ThreadName=admin-thread-pool-4854(4);|Exception while deploying t he app [myjar] : Invalid ejb jar [myjar.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 annotati ons were processed properly.|#] Could anyone please help out.