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
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
Yes, wrap it in a runtime exception. Preferebly something more concrete like IllegalStateException. Note that if the init method fails, normally the application won’t start.
You can just add the @Inject annotation to your init() method. It will get run automatically after the object is instantiated.
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