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. So, how about clean docs/samples on using CoR? (I asked about this in another thread). What about up-to-date MailReader? 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]
