[
https://issues.apache.org/jira/browse/OWB-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-499.
-------------------------------
Resolution: Not A Problem
After a bit debugging I remember that I saw this in the past as well. This is
not caused by an error in OWB but instead by jetty-maven-plugin and IDE
integrations which use src/main/webapps as the web root directory. But since
the classes will not get compiled into src/main/webapp/META-INF/classes (but
target/classes) the webs bean archive is effectively empty.
Thus adding a src/main/resources/META-INF/beans.xml is always the safe bet.
This works even if the WAR classes get jared!
> WEB-INF/beans.xml of a war will not activate Bean Archive behaviour
> -------------------------------------------------------------------
>
> Key: OWB-499
> URL: https://issues.apache.org/jira/browse/OWB-499
> Project: OpenWebBeans
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.1.0, 1.0.1
>
>
> spec section 12.1. "Bean archives" defines the following behaviour:
> The WEB-INF/classes directory of a war is a bean archive if there is a file
> named beans.xml in the WEB-INF directory of the war.
> This doesn't work in OWB currently. You can verify this by
> rm samples/guess/src/main/resources/META-INF/beans.xml
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
