[webbeans-issues] [JBoss JIRA] Resolved: (WBX-38) ServletWebBeanDiscovery should scan /META-INF/beans.xml
[
https://jira.jboss.org/jira/browse/WBX-38?page=com.atlassian.jira.plugin....
]
Dan Allen resolved WBX-38.
--------------------------
Resolution: Done
I tried to write a test for this, but I could not get the scanner to find anything when
running in standalone mode. I attempted to write an integration test, but the setup in the
servlet/tests is not quite configured correctly at the moment so all integration tests on
tomcat fail to run (at least on my machine).
ServletWebBeanDiscovery should scan /META-INF/beans.xml
-------------------------------------------------------
Key: WBX-38
URL: https://jira.jboss.org/jira/browse/WBX-38
Project: Web Beans Extensions
Issue Type: Bug
Components: Servlet Containers
Affects Versions: Servlet Containers 1.0.0.CR1
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: Servlet Containers 1.0.0.CR2
Original Estimate: 15 minutes
Remaining Estimate: 15 minutes
ServletWebBeanDiscovery.scan() looks for beans.xml rather than /META-INF/beans.xml. This
should be fixed to match the spec. The intro to chapter 11 reads:
Bean classes must be deployed in an EAR, WAR, EJB-JAR or JAR archive or directory in the
application classpath that has a file named beans.xml in the metadata directory (META-INF,
or WEB-INF in the case of a WAR). If a bean is deployed to a location that is not in the
application classpath, or does not contain a file named beans.xml in the metadata
directory, it will not be discovered by the container.
--
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