org.springframework.web.jsf Documentation Differences

This file contains all the changes in documentation in the package org.springframework.web.jsf as colored differences. Deletions are shown like this, and additions are shown like this.

If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.

Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a <code> tag will cause all subsequent paragraphs to be displayed differently.

Base class for JSF NavigationHandler implementations that want to be capable of decorating an original NavigationHandler.

Supports the standard JSF style of decoration (through a constructor argument) as well as an overloaded handleNavigation method with explicit NavigationHandler argument (passing in the original NavigationHandler). Subclasses are forced to implement this overloaded handleNavigation method. Standard JSF invocations will automatically delegate to the overloaded method, with the constructor-injected NavigationHandler as argument. @author Juergen Hoeller @since 1.2.7 @see #handleNavigation(javax.faces.context.FacesContext, String, String, NavigationHandler) @see DelegatingNavigationHandlerProxy

JSF 1.1 VariableResolver that first delegates to the original resolver of the underlying JSF implementation (for resolving managed-bean objects as defined in faces-config.xml as well as well-known implicit EL attributes), then to the Spring root WebApplicationContext (for resolving Spring beans).

Configure this resolver in your faces-config.xml file as follows:

 <application>
   ...
   <variable-resolver>org.springframework.web.jsf.DelegatingVariableResolver</variable-resolver>
 </application>

All your JSF expressions can then implicitly refer to the names of Spring-managed service layer beans, for example in property values of JSF-managed beans:

 <managed-bean>
   <managed-bean-name>myJsfManagedBean</managed-bean-name>
   <managed-bean-class>example.MyJsfManagedBean</managed-bean-class>
   <managed-bean-scope>session</managed-bean-scope>
   <managed-property>
     <property-name>mySpringManagedBusinessObject</property-name>
     <value>#{mySpringManagedBusinessObject}</value>
   </managed-property>
 </managed-bean>

with "mySpringManagedBusinessObject" defined as Spring bean in applicationContext.xml:

 <bean id="mySpringManagedBusinessObject" class="example.MySpringManagedBusinessObject">
   ...
 </bean>

@author Juergen Hoeller @since 1.1 @see WebApplicationContextVariableResolver @see FacesContextUtils#getRequiredWebApplicationContextgetRequiredWebApplicationContext @deprecated as of Spring 3.2, in favor of the JSF 1.2 based org.springframework.web.jsf.el.SpringBeanFacesELResolver

This is a subclass of the JSF 1.1 DelegatingVariableResolver, letting Spring bean definitions override other attributes of the same name.

The main purpose of this class is to provide behavior that is analogous to the JSF 1.2 org.springframework.web.jsf.el.SpringBeanFacesELResolver. @author Juergen Hoeller @since 2.5 @see WebApplicationContextVariableResolver @see FacesContextUtils#getRequiredWebApplicationContextgetRequiredWebApplicationContext @deprecated as of Spring 3.2, in favor of the JSF 1.2 based org.springframework.web.jsf.el.SpringBeanFacesELResolver

Special JSF 1.1 VariableResolver that exposes the Spring WebApplicationContext instance under a variable named "webApplicationContext".

In contrast to DelegatingVariableResolver, this VariableResolver does not resolve JSF variable names as Spring bean names. It rather exposes Spring's root WebApplicationContext itself under a special name. JSF-managed beans can then use Spring's WebApplicationContext API to retrieve Spring-managed beans, access resources, etc.

Configure this resolver in your faces-config.xml file as follows:

 <application>
   ...
   <variable-resolver>org.springframework.web.jsf.WebApplicationContextVariableResolver</variable-resolver>
 </application>

@author Colin Sampaleanu @author Juergen Hoeller @since 1.2.5 @see DelegatingVariableResolver @see FacesContextUtils#getWebApplicationContextgetWebApplicationContext @deprecated as of Spring 3.2, in favor of the JSF 1.2 based org.springframework.web.jsf.el.WebApplicationContextFacesELResolver