jboss-weld

I am using Weld as CDI implementation. My integration test, that tries to assemble object graph instantiating Weld container works well , when I have empty beans.xml in src/test/java/META-INF/beans.xml . Here is that simple test: public class WeldIntegrationTest { @Test public void testInjector() { new Weld().initialize(); // shouldn't throw exception } } Now when I run mvn clean install , I always get: Missing beans.xml file in META-INF! My root folders are "src" and "web" which contains WEB-INF folder, but I also tried to use default maven structure and renamed "web" to "webapp" and moved it

I'm trying to deal with @ManagedProperty but without success ! I've been following this guide, and it not seems that hard. But my code simply won't work! Here's a little snippet @ManagedBean @SessionScoped public class LoginBean { @EJB private LoginUserLocal loginUser; private boolean loggedIn = false; private User user; private StreamedContent image; . . . //-- @Named(value = "messagesBean") @RequestScoped public class MessagesBean { @ManagedProperty(value = "#{loginBean}") private LoginBean loginBean; public LoginBean getLoginBean() { return loginBean; } public void setLoginBean(LoginBean

I have an application with a well defined interface. It uses CDI for resolution of the modules, (Specifically it uses Instance<> injection points on API interfaces to resolve modules) and passes various data back and fourth via the interfaces without issue. I've intentionally kept the API and implementation separate, and the modules only inherit from the API to avoid tight coupling, and the application only knows of the modules through runtime dependancies, and data passing accomplished via the APIs. The application runs fine without the modules, which can be added simply by dropping the jar

Because of CDI (and its implementation Weld), every POJO in JEE6 can be annotated with @Named , which makes the POJO accessible to the view. Does that mean that ManagedBeans are completely obsolete now? Or did I miss something where @ManagedBean still makes sense? In short, @ManagedBean makes sense for applications that use JSF but do not use JSR 299 (whatever the reason is). Below a longer explanation from Gavin King: Re: Comparisons to @ManagedBean annotations in JSF2? : While looking through the Weld examples, and the older WebBeans documentation, it looks like a competitor to the new