struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eero Nevalainen <>
Subject Webwork -> Struts 2.0.x migration xwork API issue related to ProxyFactories
Date Mon, 17 Dec 2012 17:25:14 GMT

I am working on a somewhat legacy Webwork + Spring + Hibernate
application where we finally decided to bite the bullet and move to
Struts 2.0.14 from Webwork 2.2.7.

>From googling it initially seemed like the migration doesn't require
humongous effort; however there is a certain API change in xwork that
I have not seen mentioned anywhere and that I ran into. Namely, there
is class X extending DefaultActionProxyFactory, and with xwork 2 there
are two issues:

1. ActionProxyFactory is now an interface, not a class. I can't call
"setFactory(this)" in the bind() method.

2. More interestingly, it looks like in the ActionProxyFactory,
"Invocations" and "Proxies" behave differently. We used to have

    public ActionInvocation createActionInvocation(ActionProxy actionProxy)


    public ActionInvocation createActionInvocation(ActionProxy
actionProxy, Map map)

in the subclass, but now the overridable stuff is

    public ActionProxy createActionProxy(String namespace, String
actionName, Map extraContext)

I am a bit of a loss as to how to interpret the meaning of these
changes so I could meaningfully start fixing this. Any
insight/pointers as to what the relevance of this to the functioning
of the factory might be, would be greatly appreciated.

On another note, how is the compatibility of the various versions of
the spring-plugin with Spring 3.0.2 and Struts 2.0.14? Webwork worked
fine with the Spring version, but it seems to me that Struts 2.0.x
assumes something like a 2.5.x series Spring framework...

Eero Nevalainen (

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message