I am just migrating from JBoss 6.1 to Glassfish 3.1 (don't ask why). The following happens:
Invalid ejb jar [mmsUserMgmtAct-0.0.1-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.
As everything worked perfectly with Jboss, I can swear that banks have EJB. The only thing that can cause an error is that I have separated the interfaces (@Remote and @Local) plus the entities (@Entity) in the xyzService.jar package and the idle bean (@Stateless, @Remote (XyzService.class)) in another archive named xyzServiceImpl.jar.
All packaging was created by maven, so no problem with that. Maybe I should mention that I just copied this to the autodeploy folder.
Any glues?
thanks in advance El Subcomandante
source share