Interesting, when you’re using component binding on a view scoped bean, the view scope breaks. I am not sure if that is a bug in JSF2, I would have to read the entire JSF2 specification first. As far now your best bet is to drop the component binding for now and pass the selected item … Read more
You can just add the @Inject annotation to your init() method. It will get run automatically after the object is instantiated.
You’re using the wrong @SessionScoped annotation. If you’ve registered the bean with the JSF @ManagedBean annotation, then you need to import the @SessionScoped from the JSF (javax.faces) package as follows: import javax.faces.bean.SessionScoped; When you incorrectly use a CDI scope on a JSF managed bean, then there is effectively no JSF scope for the JSF managed … Read more
That can happen when the message component is rendered before the message is added. In your specific example, the bean is referenced for the first time by the <h:outputText> component and thus constructed for the first time at that moment. But the <h:outputText> component appears in your specific example after the <p:messages> component, so the … Read more
When should one use the f:viewAction or preRenderView event to initialize data for a page verses using the @PostConstruct annotation? Use the <f:viewAction> when you want to execute a method before the HTML is been rendered. This is particularly useful if you want to perform actions based on model values set by <f:viewParam> during update … Read more
In other words, your @ViewScoped bean behaves like a @RequestScoped bean. It’s been recreated from scratch on every postback request. There are many possible causes for this, most of which boils down that the associated JSF view is not available anymore in the JSF state which in turn is by default associated with the HTTP … Read more