On 6/12/06, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
We have a Wiki page that I
started that I actually think, in a more grand form probably, would do
the tricknicely... it would basically just be a catalog of things in
SAF1 and how to do something analogous in SAF2.  I think if we all
pitched in and built that up, answered as many of those types of
questions before-hand as we can, I actually don't think we have to worry
about a migration path at all.  Sure, still bring forward the features
that everyone likes, that's completely reasonable, but beyond that I
think there may not be too much point in thinking about migration and
compatibility at all.

Hmmm, well guides like the one you describe *are* thinking a lot about
migration and compatibility, just not binary "out-of-the-box" backward
compatability. But, since this is a major release, and therefore by
definition a revolution, i think that's OK.

There's another page comparing SAF1 and SAF2 from a high-level here:

* http://confluence.twdata.org/display/WW/Comparing+SAF1+and+SAF2

I also went ahead and moved the Struts Action 2 migration material
into the SAF2 documentation.

* http://confluence.twdata.org/display/WW/Migration+Guide

Meanwhile, we've migrated the MailReader to WW2

* http://svn.apache.org/viewvc/struts/sandbox/trunk/action2/apps/mailreader/src/

and the next step is to move it to the latest SAF2 build. It would
then be interesting to do some 1:1 comparisons of SAF1 and SAF2
idioms. I'd also like to migrate the iBATIS Petstore application,
since many people have used that application as a starting point. It
would also be interesting, but not trivial, to migrate XPlanner and
Roller.

My suggestion is that any migration guides or tools should be based on
our own actual experience -- which is the whole idea behind open
source. We eat our own dog food, and then we pass the bowl. (Yumm!
Just the thing to read over breakfast!)

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to