> [migration classes]
> > These were added by Patrick a while back, and it was decided to remove
> > them, rather than carry over old stuff. It's suggested that you extend
> > from com.opensymphony.xwork.ActionSupport instead, possibly having a
> > parent class for your actions which provides the c
>A) a list of docs that we need to help migration would be _fantastic_.
>Perhaps create a skeleton on the Wiki with the points you had trouble with?
>I'd be more than happy to fill out the content.
Well I'm slowly going through the migration proccess myself, and I'm writing
notes along the way.
>
Anders,
Well - those are interesting points.
A) a list of docs that we need to help migration would be _fantastic_.
Perhaps create a skeleton on the Wiki with the points you had trouble with?
I'd be more than happy to fill out the content.
B) The *Aware interfaces are interesting - they have bee
[migration classes]
> These were added by Patrick a while back, and it was decided to remove
> them, rather than carry over old stuff. It's suggested that you extend
> from com.opensymphony.xwork.ActionSupport instead, possibly having a
> parent class for your actions which provides the calls to do
See below...
> -Original Message-
> From: boxed [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 02, 2003 3:59 PM
> To: [EMAIL PROTECTED]
> Subject: [OS-webwork] WW2 migration
>
>
> I have tried migrating my quite large app to WW2, these are
> my
Yeah, we're definitely lacking on the docs. My schedule will be freeing
up in two weeks so I'll be able to put more effort into that.
M
boxed wrote:
I have tried migrating my quite large app to WW2, these are my issues with
it:
http://wiki.opensymphony.com/space/WebWork+2+Migration+Guide specif
I have tried migrating my quite large app to WW2, these are my issues with
it:
http://wiki.opensymphony.com/space/WebWork+2+Migration+Guide specifies that:
>ActionSupport has moved from webwork.ActionSupport to
com.opensymphony.xwork.ActionSupport,
> but a deprecated webwork.ActionSupport and webw
