[
https://issues.jboss.org/browse/CDI-218?page=com.atlassian.jira.plugin.sy...
]
jaikiran pai commented on CDI-218:
----------------------------------
I have been reading Pete's blog about CDI 1.1 Public review draft of the spec and
noticed this JIRA and the changes being proposed. FWIW, in Java EE6, it's only JPA
which has been inconsistent on where the deployment descriptor (persistence.xml) is
expected to be placed. It expects it to be under .war/WEB-INF/classes/META-INF. The EJB
3.1 spec (just like CDI 1.0 spec) expects ejb-jar.xml to be under .war/WEB-INF folder. So
I'm not sure if allowing beans.xml in .war/WEB-INF/classes/META-INF is going to help
much in fixing that inconsistency or if it's going to make it a bit more
inconsistent.
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