[
https://jira.jboss.org/jira/browse/JBMETA-208?page=com.atlassian.jira.plu...
]
jaikiran pai commented on JBMETA-208:
-------------------------------------
> 4. If it contains neither a DTD nor a namespace, display a
warning that you are entering 'compatibility mode' where you both process the
ejb-jar.xml and scan for annotations (at the expense of reduced startup time). The warning
should advise the developer 'either add a DTD or a namespace to avoid this
warning'
IMO, it should print out a WARN that will inform the user/dev that the deployment will
*not* be scanned for annotations. The developer can then fix it appropriately. This nicely
fits in with the requirement that
1) EJB3 deployment require a namespace
2) User being notified of an incorrect ejb-jar.xml
3) No additional performance cost.
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira