> [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 doExecute, > > etc. > > I can see you don't want legacy stuff in xwork/ww2. What I don't see is why > you actually want to, and excuse my language, fuck the users over. If you > want to make migration from ww1 to ww2 to be this hard, then a rename is > seriously overdue, because it's not version 2, it's a totally new thing. > > Put migration stuff in a separate package. I said this when ww2 was just a > twinkle in pats eye and I wonder what happened during the short time I > wasn't around to be a total ass on this list. You decided users were > irrellevant? Or just that a new package was too much hassle? I really don't > understand.
Alright alright, settle down. I'll put them back in and make the build create a webwork-migration.jar or something of that sorts. -Pat ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
