Home » xwork-2.1.5 » com.opensymphony » xwork2 » spring » interceptor » [javadoc | source]
public class: ActionAutowiringInterceptor [javadoc | source]

All Implemented Interfaces:
    org.springframework.context.ApplicationContextAware, Interceptor

TODO: Give a description of the Interceptor. TODO: Describe the paramters for this Interceptor. TODO: Discuss some possible extension of the Interceptor.

<!-- TODO: Describe how the Interceptor reference will effect execution -->
<action name="someAction" class="com.examples.SomeAction">
     TODO: fill in the interceptor reference.
    <interceptor-ref name=""/>
    <result name="success">good_result.ftl</result>

Autowires action classes to Spring beans. The strategy for autowiring the beans can be configured by setting the parameter on the interceptor. Actions that need access to the ActionContext can implements the ApplicationContextAware interface. The context will also be placed on the action context under the APPLICATION_CONTEXT attribute.
Field Summary
public static final  String APPLICATION_CONTEXT     
Method from com.opensymphony.xwork2.spring.interceptor.ActionAutowiringInterceptor Summary:
getApplicationContext,   intercept,   setApplicationContext,   setAutowireStrategy
Methods from com.opensymphony.xwork2.interceptor.AbstractInterceptor:
destroy,   init,   intercept
Methods from java.lang.Object:
clone,   equals,   finalize,   getClass,   hashCode,   notify,   notifyAll,   toString,   wait,   wait,   wait
Method from com.opensymphony.xwork2.spring.interceptor.ActionAutowiringInterceptor Detail:
 protected ApplicationContext getApplicationContext() 
 public String intercept(ActionInvocation invocation) throws Exception 
    Looks for the ApplicationContext under the attribute that the Spring listener sets in the servlet context. The configuration is done the first time here instead of in init() since the ActionContext is not available during Interceptor initialization.

    Autowires the action to Spring beans and places the ApplicationContext on the ActionContext

    TODO Should this check to see if the SpringObjectFactory has already been configured instead of instantiating a new one? Or is there a good reason for the interceptor to have it's own factory?

 public  void setApplicationContext(ApplicationContext applicationContext) throws BeansException 
 public  void setAutowireStrategy(Integer autowireStrategy)