2012/12/18 Eero Nevalainen :
> To respond to my own post to record a bit more information about the
> actual problem here, in case someone has any ideas:
>
> What the xwork 1-style ActionProxyFactory does is that it returns an
> ActionInvocation. Our legacy code further extends the
> DefaultActionI
To respond to my own post to record a bit more information about the
actual problem here, in case someone has any ideas:
What the xwork 1-style ActionProxyFactory does is that it returns an
ActionInvocation. Our legacy code further extends the
DefaultActionInvocation in order to get to override cr
2012/12/17 ChadDavis :
> I don't have answers to your specific questions, but I did do a similar
> migration recently. I encountered one fairly significant hidden issue that
> I'll warn you about. When you migrate, you can leave your xml on the
> xworks dtds. It works, but as you migrate up the
I don't have answers to your specific questions, but I did do a similar
migration recently. I encountered one fairly significant hidden issue that
I'll warn you about. When you migrate, you can leave your xml on the
xworks dtds. It works, but as you migrate up the struts2 versions, there's
a poi
Hi,
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
5 matches
Mail list logo