users@glassfish.java.net

basic glassfish error on jboss toool+eclipse + seam

From: <glassfish_at_javadesktop.org>
Date: Sat, 04 Apr 2009 16:08:57 PDT

I just tried to get an 'out of the box' seam 2.1.1GA app to deploy to glassfish (glassfish-installer-v2.1-b60e-windows) and get an error.

This is as basic as you get.

0. download latest v2.1 glassfish
1. download eclipse
2. install jboss tools
3. create eclipse server pointing to latest glassfish v2.1 download
4. configured mysql pool/datasource tested and pinged okay
4. create new seam web project (starter project in eclipse). This auto deploys ( i think as exploded archive).


this is what i get in the console log

---
SEVERE: Exception occured in J2EEC Phasejava.lang.IllegalArgumentException: Invalid ejb jar [jboss-seam.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), please check server.log to see whether the annotations were processed properly.
com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [glassfish-ear] -- Invalid ejb jar [jboss-seam.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), please check server.log to see whether the annotations were processed properly.
	at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:406)
	at com.sun.enterprise.deployment.backend.AppDeployerBase.loadDescriptors(AppDeployerBase.java:359)
	at com.sun.enterprise.deployment.backend.AppDeployer.explodeArchive(AppDeployer.java:303)
	at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:207)
	at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:148)
	at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:208)
	at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
	at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:966)
	at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:283)
	at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:835)
	at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187)
	at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:225)
Caused by: java.lang.IllegalArgumentException: Invalid ejb jar [jboss-seam.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), please check server.log to see whether the annotations were processed properly.
	at com.sun.enterprise.deployment.util.EjbBundleValidator.accept(EjbBundleValidator.java:95)
	at com.sun.enterprise.deployment.util.ApplicationValidator.accept(ApplicationValidator.java:82)
	at com.sun.enterprise.deployment.EjbBundleDescriptor.visit(EjbBundleDescriptor.java:730)
	at com.sun.enterprise.deployment.Application.visit(Application.java:1819)
	at com.sun.enterprise.deployment.archivist.ApplicationArchivist.validate(ApplicationArchivist.java:520)
	at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:382)
	... 11 more
WARNING: Undeployment of component [glassfish-ear] failed. Component [glassfish-ear] is not registered.
INFO: ADM1064:The upload file at [C:\Documents and Settings\Will\Local Settings\Temp\s1astempdomain1server-1281501540\glassfish-ear.ear] exists and will be overwritten.
INFO: ADM1006:Uploading the file to:[C:\Documents and Settings\Will\Local Settings\Temp\s1astempdomain1server-1281501540\glassfish-ear.ear]
SEVERE: Exception occured in J2EEC Phasejava.lang.IllegalArgumentException: Invalid ejb jar [jboss-seam.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), please check server.log to see whether the annotations were processed properly.
com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [glassfish-ear] -- Invalid ejb jar [jboss-seam.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), please check server.log to see whether the annotations were processed properly.
	at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:406)
	at com.sun.enterprise.deployment.backend.AppDeployerBase.loadDescriptors(AppDeployerBase.java:359)
	at com.sun.enterprise.deployment.backend.AppDeployer.explodeArchive(AppDeployer.java:303)
	at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:207)
	at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:148)
	at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:208)
	at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
	at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:966)
	at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:283)
	at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:835)
	at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187)
	at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:225)
Caused by: java.lang.IllegalArgumentException: Invalid ejb jar [jboss-seam.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), please check server.log to see whether the annotations were processed properly.
	at com.sun.enterprise.deployment.util.EjbBundleValidator.accept(EjbBundleValidator.java:95)
	at com.sun.enterprise.deployment.util.ApplicationValidator.accept(ApplicationValidator.java:82)
	at com.sun.enterprise.deployment.EjbBundleDescriptor.visit(EjbBundleDescriptor.java:730)
	at com.sun.enterprise.deployment.Application.visit(Application.java:1819)
	at com.sun.enterprise.deployment.archivist.ApplicationArchivist.validate(ApplicationArchivist.java:520)
	at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:382)
	... 11 more
---
layout looks a little odd on the server.
in the applications\j2ee-apps\ dir i get my app as 
\glassfish-ear
    \glassfish-war
         \...
    \jboss-seam-jar
        jboss-seam.jar
    - antlr-runtime.jar
    - drools-compiler.jar
    - drools-core.jar
    - jboss-el.jar
    - jbpm-jpdl.jar
    - mvel14.jar
    - richfaces-api.jar
this is odd as in eclipse the jboss-seam.jar is just another jar in the EarContent dir.
the only difference  is the application.xml in the ear declares jboss-seam.jar as an ejb module.
I see other threads with something similar see
http://forums.java.net/jive/message.jspa?messageID=227470  
buts doesnt really tell me what the problem is.  Does any one know how this is resolved so I can get seam up in glassfish ?
[Message sent by forum member 'wiggy' (wiggy)]
http://forums.java.net/jive/thread.jspa?messageID=340612