This works only with the in JSF 2.3 introduced javax.faces.annotation.ManagedProperty. @Inject @ManagedProperty(“#{param.id}”) private String id; The now deprecated javax.faces.bean.ManagedProperty annotation works only in JSF @ManagedBean classes. I.e. in instances which are managed by JSF. It does not work in instances which are managed by CDI @Named. Further, you’ve made another mistake: you’re trying to prepare … Read more
For EJB and JAR packaging you should place the beans.xml in src/main/resources/META-INF/. For WAR packaging you should place the beans.xml in src/main/webapp/WEB-INF/. Remember that only .java files should be put in the src/main/java and src/test/java directories. Resources like .xml files should be in src/main/resources.
You are mixing JSF managed beans with CDI beans. Your LoginBean is a JSF managed bean (it has the @ManagedBean annotation). Your MessageBean is a CDI bean (it has the @Named annotation). If you changed the Message bean to a JSF managed bean (replacing @Named with @ManagedBean) then the problem should be solved (It should … Read more
To inject an instance of class C: javax.enterprise.inject.spi.CDI.current().select(C.class).get() This is available in CDI 1.1+
If you can upgrade to JSF 2.2, immediately do it. It offers a native @ViewScoped annotation for CDI. import javax.faces.view.ViewScoped; import javax.inject.Named; @Named @ViewScoped public class Bean implements Serializable { // … } Alternatively, install OmniFaces which brings its own CDI compatible @ViewScoped, including a working @PreDestroy (which is broken on JSF @ViewScoped). import javax.inject.Named; … Read more
The @EJB is used to inject EJB’s only and is available for quite some time now. @Inject can inject any managed bean and is a part of the new CDI specification (since Java EE 6). In simple cases you can simply change @EJB to @Inject. In more advanced cases (e.g. when you heavily depend on … Read more
javax.enterprise.context.SessionScoped(JSR 346) and all other annotations under the javax.enterprise.context.* package maintain the context of CDI. CDI provides an alternative, versatile and more powerful mechanism for dependency injection, bean and general resource management within the Java EE space. It’s an alternative to JSF managed beans and it’s set to even supersede the JSF bean management mechanism … Read more
First of all let me do some clarifications: Managed bean definition : generally a managed bean is an object that its life cycle (construction, destruction, etc) is managed by a container. In Java ee we have many containers that manage life cycle of their objects, like JSF container, EJB container, CDI container, Servlet container, etc. … Read more
because when the constructor is called, the bean is not yet initialized – i.e. no dependencies are injected. In the @PostConstruct method the bean is fully initialized and you can use the dependencies. because this is the contract that guarantees that this method will be invoked only once in the bean lifecycle. It may happen … Read more
Tomcat as being a barebones JSP/Servlet container doesn’t support CDI out the box. How exactly did you install CDI? Did you really drop jakartaee-api.jar or javaee-api.jar in /WEB-INF/lib just to get your code to compile? Oh please no, this is not the right way. The JEE API JAR contains solely the API classes, not the … Read more