I have the same problem.
I have created both Stateless Session Bean and Entity Beans. These files/EJBs deploy fine under Kodo JPA implementation in Weblogic. I was able to run test cases via stand-alone java client (unit test client using testng).
But once I deployed the .ear file in Glassfish, I also got the same error:
[#|2007-07-05T18:29:00.167-0700|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=12;_ThreadName=Timer-5;Error loading deployment descriptors for module [ams] -- Invalid ejb jar [ams.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.
;_RequestID=3240e556-0f00-4e50-bec3-a3651c5fc5de;|"DPL8011: autodeployment failure while deploying the application : Error loading deployment descriptors for module [ams] -- Invalid ejb jar [ams.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.
"|#]
Based on the comments, I just download the v1 patch 01 and v2 beta and tried both versions. The result is the same. Glassfish still won't deploy and with above errors.
I don't know why @Entity is not an ejb component. I thought it is called EJB entity Bean.
Whatever it is, I can't simply deploy the working EJB ear files.
Chester
[Message sent by forum member 'chesterxgchen123' (chesterxgchen123)]
http://forums.java.net/jive/thread.jspa?messageID=225422