[Goldenits]

Hi there.

I created an ejb3 project (J2EE5) in my myeclipse workspace. The project has two project dependencies to other ejb projects. The other projects deploy fine, but when I try to deploy the project to the confiured glassfish application server (runs under JDK 1.6), I get the following exception:

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.EjbBundleDescriptor.visit(EjbBundleDescriptor.java:729)
at com.sun.enterprise.deployment.archivist.EjbArchivist.validate(EjbArchivist.java:190)
at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:790)
at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:744)
at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:349)
… 32 more

There are definitely session beans in the project and I don’t know why I keep getting this exception. I also posted this question in the Java dev forum, but I post it here too. Could it be a problem with the myeclipse J2EE libraries?

Thanks for any help!

[Loyal Water]

This is possibly a bug which has not been resolved yet:-
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6540941

You might have to check with the Glassfish team.

[Author]

Posts