> I am currently migrating a much bigger app I have been working on for 4 > years. With this significant code base, I found no issues in my test appart > from this beans.xml / bean annotated mode issue.
Wow, thanks a lot Ludovic! That’s great news! I’ve (hopefully) already fixed this bug in trunk yesterday night. Could you please be so kind and test this as well? A note of caution: If you debug your application with IDEA, Eclipse or the tomcat7-maven-plugin, then you might end up having your classes NOT in WEB-INF/classes but somewhere in target/classes. That way we cannot detect that this is the class folder which belongs to WEB-INF/beans.xml. Thus I personally prefer to have the beans.xml info in src/main/resources. That way it also works if you decide to package your web classes into a jar (maven-war-plugin option ‚archiveClasses‘). The only reason I have a WEB-INF/beans.xml is when I know that the project _also_ needs to run on WebSphere. WAS _only_ activates CDI if you have the marker file in WEB-INF. LieGrue, strub > Am 11.05.2015 um 14:22 schrieb [email protected]: > > On 09/05/2015 08:17, Mark Struberg wrote: >> Txs Ludovic! >> >> Will check it in the evening. Today is full with preparation with kids for >> mothers day tomorrow ;) > Dear all. I sat Gerhard opened a bug on JIRA for this issue : > > https://issues.apache.org/jira/browse/OWB-1071 > > This kind of reassured me as I was reading over and over the CDI 1.2 spec and > did not find something about a different behavior whether the beans.xml file > is in WEB-INF or META-INF. ;-) > > Anyway, just to thank you for your incredible work and impressive reactivity. > > I am currently migrating a much bigger app I have been working on for 4 > years. With this significant code base, I found no issues in my test appart > from this beans.xml / bean annotated mode issue. > > Ludovic > | > | AVANT D'IMPRIMER, PENSEZ A L'ENVIRONNEMENT. > | >
