[
https://issues.jboss.org/browse/CDI-218?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-218:
-----------------------------------
I'd rather say it the other way around: ejb-jar.xml is the _only_ exception ;)
MANIFEST.MF e.g. is the oldest of this kind of files and it is perfectly fine in both
locations. As all other XML or similar files which contain additional info (properties,
etc) are perfectly fine in WEB-INF/classes/...
Honor WEB-INF/classes/META-INF/beans.xml to activate WEB-INF/classes
a bean archive
-----------------------------------------------------------------------------------
Key: CDI-218
URL:
https://issues.jboss.org/browse/CDI-218
Project: CDI Specification Issues
Issue Type: Clarification
Components: Packaging and Deployment
Reporter: Dan Allen
Assignee: Pete Muir
Priority: Minor
Fix For: 1.1.PRD
Chapter 12.1 specifies that beans.xml must be in the WEB-INF directory of a web archive
to activate the WEB-INF/classes directory of that war as a bean archive (and thus make
java:comp/BeanManager visible to the web app).
However, many developers find this location both confusing and inconvenient at times. The
instinct of many developers is to put the beans.xml in WEB-INF/classes/META-INF since that
follows the convention that applies to library jars.
Obviously, we cannot break backwards compatibility. Therefore, this issue proposes to
honor either location in the war:
- WEB-INF/beans.xml
- WEB-INF/classes/META-INF/beans.xml
If both files are present, the WEB-INF/beans.xml should take precedence and a warning is
recommended. (Merging them is not likely the behavior that a developer would want).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira