faces-config

Is there any way to get the <to-view-id> of a navigation case in the backing bean? Let's say I want to get the <to-view-id> from the outcome success , which is supposed to be page1.xhtml . Is there any helper function? <navigation-rule> <from-view-id>start.xhtml</from-view-id> <navigation-case> <from-action>#{pageController.processPage1}</from-action> <from-outcome>success</from-outcome> <to-view-id>page1.xhtml</to-view-id> </navigation-case> <navigation-case> <from-action>#{pageController.processPage2}</from-action> <from-outcome>success</from-outcome> <to-view-id>page2.xhtml</to-view-id> <

In my application in some places we are using @ManagedBean annoation for Person bean and for the same Person bean we defining in the faces-confing.xml like below at the same time. @ManagedBean("name=person") @SessionScoped Public class Person{ } faces-config.xml <managed-bean> <managed-bean-name>person</managed-bean-name> <managed-bean-class>com.test.sample.Person</managed-bean-class> <managed-bean-scope>session</managed-bean-scope> </managed-bean> my question is does this approach create two instances for the Person bean or it does matter if I do this? Does this have any effect on performance

While working on a Spring-JSF integration, I'm seeing this entry in faces-config.xml . <application> <el-resolver> org.springframework.web.jsf.el.SpringBeanFacesELResolver </el-resolver> </application> Can someone explain what exactly <application> and <el-resolver> are? BalusC <application> represents the JSF application . Exactly the one as you can obtain as Application application = FacesContext.getCurrentInstance().getApplication(); <el-resolver> represents the EL resolver as used by JSF application . Exactly the one as you can obtain as ELResolver elResolver = application.getELResolver();

Have the following code snippets: Bean: import javax.faces.view.ViewScoped; import javax.inject.Named; @Named(value = "directoryBean") @ViewScoped public class DirectoryBean implements Serializable { private static final long serialVersionUID = 1L; .... } faces-config.xml <?xml version="1.0" encoding="UTF-8"?> <faces-config xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_3.xsd" version="2.3"> .... </faces-config> group.xhtml <ui

After the JSF 2 big support for annotations, I'm wondering what I would use the faces-config.xml for. What is its importance now? In other words, what are the configurations that can only be done through faces-config.xml and not via annotations? Right now all what I am using it for is to declare Spring's EL resolver. <?xml version="1.0" encoding="UTF-8"?> <faces-config xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd" version="2.0">