DelegatingActionProxy

[asarco]

Hello,

What's the point of using DelegatingActionproxy instead of simply WebApplicationContextUtils.getWebApplicationContex t(servletContext); inside every action? I see many cons:

There is one more xml file (action-servlet.xml)
Have to define every action as a bean.
From the struts-config, you cannot tell what actions maps to what path, because all path point to DelegatingActionProxy.

How can I convice my boss and co-workesrs to use DelegatingActionProxy?

[irbouho]

How can I convice my boss and co-workesrs to use DelegatingActionProxy?

You do not need to
You can continue to use Struts the old way (struts-config.xml, actions, action forms) but extends org.springframework.web.struts.XXXActionSupport instead of Struts own XXXAction. This approach, however, does not allow for using all the features of Spring MVC (Interceptors, HandlerMapping, View, ViewResolver...) but is, IMHO, the fastest way to integrate Struts with Spring.
HTH