This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
build 060523 glassfish b48 -install glassfish -start IDE with clean userdir -register glassfish in the IDE -create EJB module -create some entity classes -deploy module -ERROR: module is not deployed and here is error message: ... Finished registering server resources deployment started : 0% Deploying application in domain failed; Deployment Error -- null /home/honza/EJBModule2/nbproject/build-impl.xml:312: Deployment error: The module has not been deployed. See the server log for details. BUILD FAILED (total time: 6 seconds)
increasing priority to P1, reproducible on 3 machines with glassfish b48
can duplicate. When did this work?
Is not it a duplicate of a P2 where when you deploy an ejbmodule without EJBs (entity beans are not EJBS), the deployment fails? Can you try on JBoss? If yes, the IDE should also validate an EJB Module before the deployment... So we can fix this in the right place for all the servers, not only GlassFish (that could obvioulsy do a better user error reporting)
read http://www.netbeans.org/issues/show_bug.cgi?id=50323 This old bug is for j2ee 1.4 when ejb-jar.xml was mandatory. It is not anymore for java ee 5... Same root cause regarding validation before deployment from the IDE?
Workaround is to add EJBs in EJB Module: This is what EJB modules are for: to contain EJBs (at least 1) The error reporting is ugly, but the error is reported: the module cannot be deployed. See the duplicated bug to see the corresponding GlassFish issue that has been filed as well for better error handling. I would prefer to fix this on the Nb side than the plugin side, since all servers will benefir from this verification step done at the IDE level. *** This issue has been marked as a duplicate of 50323 ***