Hello all!
During an EAR deployment Glassfish v2 b58g complaints if one declares an
EJB module which only contains EJB 3.0 style entities (annotated POJOs)
and forces one to package them as a Java library. Is there really a need
to do that according to confirm with the EJB 3.0 spec? I ask as other
implementations don't force the application assembler to package his
application in this way.
The output in server.log states "A valid ejb jar requires at least one
session, entity (1.x/2.x style), or message driven bean."
Could someone please point me to the source of this requirement in the
EJB 3.0 spec! I couldn't find it. Although I agree it is perfectly fine
to package those annotated POJOs in a plain java library and reference
it in persistence.xml I don't understand why to force the application
provider to do it in this way.
Regards,
Eric
--
Eric Hubert
Software Architect
Associate Director Research & Development