On 6/12/06, Don Brown <[EMAIL PROTECTED]> wrote:

On 6/12/06, Ted Husted <[EMAIL PROTECTED]> wrote:
> On 6/12/06, Don Brown <[EMAIL PROTECTED]> wrote:
> > Please let us know your thoughts so we can focus on developing tools
> > to make migration as easy as possible.  Thanks,
>
> My first thought would be how would migrating one part without the
> others would serve any practical purpose?

In some cases, I think so.  For example, it might be nice to reuse
validator configurations or custom ActionForms.  I'm thinking we could
support either pretty easily.  Struts Actions, on the other hand, are
more difficult since they depend on ActionForms, but it could probably
be done with a proxy Action and a bunch of parameters.

> My second thought would be how often would production-applications
> actually be migrated?

That is a good question and one I'm trying to answer here as well.  I
want to make sure the time spent on migration tools will be productive
and user's fears of being left behind are mitigated.  Personally, I've
migrated my current Struts application to Action 2, but plan to leave
the rest alone because, right, if it isn't broken, why fix it.


There are also the cases where an existing app is going to be substantially
re-implemented, and the natural question will be whether or not to upgrade
the underlying framework to take advantage of new features.  If SAF2 doesn't
even pay lip service to a migration story (which'd be pretty ironic of the
lambasting that Shale got over wanting the "Struts" brand :-), then you're
not giving the existing users much incentive to migrate to SAF2 versus any
other framework.

Don


Craig



> In the field, it seems like that once a Struts application hits
> production, it continues to use the same version. A new application
> might use 1.2, but the old ones continue to plug along on 1.1. If it
> ain't broke, why fix it?
>
> -Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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


Reply via email to