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
You can put common resources in the /META-INF/resources folder of the JAR which is to be treated like as /WEB-INF/resources folder of the WAR. E.g. CommonWebProject |– META-INF | |– resources | | `– common | | |– css | | | `– some.css | | |– js | | | `– some.js | | … Read more
You probably already know that PrimeFaces is using jQuery under the covers. PrimeFaces Selectors are based on jQuery. Anything which you specify in @(…) will be used as jQuery selector on the current HTML DOM tree. For any found HTML element, which has an ID, exactly this ID will ultimately be used in the update. … Read more
This concern is unnecessary. You can safely have multiple servlets in a single web application, as long as their URL patterns do not clash with each other. Usually, if that were the case, a bit sane servlet container would already throw an exception during webapp’s startup. In your case, you’ve registered the JSF servlet on … Read more
The view build time is not a phase. The view build time is that moment when the physical UIViewRoot instance and all of its children is built based on the view declaration, which is usally defined in XHTML or JSP files. The view build time moment is not restricted to a specific JSF lifecycle phase. … Read more
A @ViewScoped bean lives exactly as long as a JSF view. It usually starts with a fresh new GET request, or with a navigation action, and will then live as long as the enduser submits any POST form in the view to an action method which returns null or void (and thus navigates back to … Read more
Put the bean in the view scope and get rid of any business logic in getter methods. The bean must be placed in the view scope so that all previous selections and new available items are remembered for subsequent postbacks, otherwise things will fail when JSF needs to validate the selected item against the list … Read more
Technically, it doesn’t matter where you declare the <f:metadata> in the view as long as it’s in the top level view (so, when using templating, in the template client and thus not in the master template). When the view get built, the metadata is basically not part of the JSF component tree, but of the … Read more
This approach will not work. You seem to be confusing/mixing the basic web development concepts of the “server side” and “client side” and to be misunderstanding the role of JSF and EL. JSF is a server side language which runs on the webserver upon a HTTP request and produces HTML/CSS/JS code which get returned with … Read more
PrimeFaces will auto-include the necessary JS/CSS resources in <h:head>. However, you don’t have that tag. You’ve there a “plain HTML” <head>. Fix it accordingly: <html> <h:head> … </h:head> <h:body> … </h:body> </html> This mistake should also have been logged in the server log as below: One or more resources has the target of ‘head’ but … Read more