On 2/16/06, Michael Jouravlev <[EMAIL PROTECTED]> wrote: > > On 2/16/06, Martin Cooper <[EMAIL PROTECTED]> wrote: > > Amongst other things, 1.3 brings a clean way of implementing your action > > mappings as chains of commands instead of using actions. That alone > makes it > > stand out from 1.2. I like it a lot. At the same time, you can still use > > actions if you want to, which makes it a great platform ifor when you > need > > to be able to reuse some of the work you've put in on 1.2 or earlier > > applications. > > Backward compatibility is great. Considering chain of commands, do you > really think that someone who supports a legacy app, will get to > refactor it with chain? (Unless this someone already did it a year ago > using nightly build ;-) ). I mean, how the learning curve for 1.3 CoR > compares with learning curve for WebWork and interceptors? Therefore I > have doubts that CoR will be used widely, outside of early adopters' > circle. But I am glad that it finally is about to make it officially.
The chain stuff is actually available in 1.2.x as well, as an add-on package, so it's not exactly new news. It's been available for 2-1/2 years now. It's just that it's not as cleanly integrated in 1.2 as it is in 1.3. I was actually talking about forwards compatibility, rather than backwards compatibility. If I'm building a new app using 1.3, and I realise that I need some of the same functionality that I built into an earlier 1.2 app, I can, assuming I structured my actions properly, simply pick up my existing actions and drop them into my 1.3 app, even if the rest of the app is built using chains. But even for someone who's working on a legacy app, moving to 1.3 will allow them to use chains for new parts of the application if they want to, leaving the rest using actions. The learning hump for using chains is very, very low. So, how about clean docs/samples on using CoR? (I asked about this in > another thread). What about up-to-date MailReader? Volunteers are always welcome. ;-) -- Martin Cooper To my shame, I have > not looked into CoR since my last surge of interest in September last > year. Frankly, I am pretty happy with 1.2.x (or maybe I am just lazy). > > The docs/samples will be the major factor for adoption among Struts > 1.2.x public. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
