[jboss-jira] [JBoss JIRA] Commented: (JBMETA-208) Prescence of an ejb-jar.xml without a namespace stops annotation-based metadata processing

> And if it's EJB2 then does it make sense to look into each class in the JAR to make sure there are no EJB3 annotations? Because this is what you are asking for.

From my understanding, that's *not* what Richard is asking for. I guess, the point he is trying to make is (based on what i see in the forum post) that some of the deployers processed this as a EJB3 deployment where as the others did not process it. Effectively, this resulted in the deployment having insufficient metadata. As shown in the logs, in that post, we did create the EJB3 services for this deployment (we shouldn't have):

Prescence of an ejb-jar.xml without a namespace stops annotation-based metadata processing ------------------------------------------------------------------------------------------ Key: JBMETA-208 URL: https://jira.jboss.org/jira/browse/JBMETA-208 Project: JBoss Metadata Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 1.0.1.GA Environment: JBoss AS 5.1.0.GA Reporter: Richard Kennard Assignee: Alexey Loubyansky The presence of a META-INF/ejb-jar.xml file that is not properly namespaced, for example... <ejb-jar> </ejb-jar> ...instead of... <ejb-jar version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"> </ejb-jar> ...stops ALL of the annotation-based metadata processing. Every session bean in the JAR reports with the JBMETA-4 warning, and therefore none of them get registered with JNDI. This is much worse than simply ignoring the ejb-jar.xml altogether, as is arguably acceptable as it isn't namespaced. An un-namespaced ejb-jar.xml is not uncommon. Many examples, including this one from the JBoss documentation... http://docs.jboss.org/ejb3/app-server/reference/build/reference/en/html/p... ...leave off the namespace, so for JBoss to fail without warning seems a little harsh. Leaving off the namespace worked fine in JBoss 4.2.3.GA.