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.
From the forum questions/mailing list questions, we noticed netbeans tend to package invalid ejb jar which contains no ejb. See http://www.netbeans.org/issues/show_bug.cgi?id=50323 for some additional information. Per Petr Blaha's request, I am opening this new bug. (Ludo has already sent the necessary code to the netbeans team). According to the spec, valid ejb jar should contain at least one ejb. This means the ejb jar need to either 1. include a valid ejb-jar.xml which declares at least one of the session bean, entity bean or message drive bean. Or 2. has at least of one of the ejb component level annotations: @Stateful, @Stateless and @MessageDriven. Note: @Entity is not a ejb component level annotations. EJB30 entity objects are POJO. This type of invalid packaged ejb jar: 1. if in ear form: in the application.xml, this jar is declared as an ejb module 2. if in standalone ejb jar form: it contains an empty ejb-jar.xml (this case will trigger schema validation error), or it contains an empty sun-ejb-jar.xml. The most common use case we saw (which are posted in the forum or mailing list) is packaging persistence units (with @Entity annotation) as ejb jar.
The bug is duplicate of the issue #50323. I didn't understand correctly one Hong's comment and asked him to create new bug. It was my mistake. *** This issue has been marked as a duplicate of 50323 ***