Andy: Just to second what Dave said:
I reluctantly switched over to 1.12b a month or so ago. I was reluctant because I am in the middle of learning Struts and converting an existing app over to it, and I had enough to handle without worrying about the changes between 1.02 and 1.1. I switched, finally, because my reading proved that there were a number of new features that I could not ignore. If I did, I was going to have to code them -- with difficulty -- to 1.02 functionality, only to then turn around and re-code them very easily to new 1.1 capabilities. First and most importantly, the switch caused *NO* errors. I simply replaced the Struts version and everything still worked. I then started implementing the new features as I needed them. I replaced deprecated method calls where it was easy and where it made sense; others I left alone for the foreseeable future. When I get everything working, I'll go back and make a cleanup pass, removing calls to deprecated methods. The validator and declarative exception handling alone are worth the price of admission. I haven't even touched DynaForms yet, which I know is a big new capability and very worthwhile. Other worthwhile new stuff abounds; use what you need and ignore the rest until you do need it. -----Original Message----- From: David Graham [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 12:13 PM To: [EMAIL PROTECTED] Subject: Re: 1.1 release date? I understand not wanting to use a beta version but it has really worked well for me. All the stuff I was using in 1.0.2 still works and the new stuff I've tried works as well (plugins, map backed form fields, exception handling). Dave >From: Eddie Bush <[EMAIL PROTECTED]> >Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> >To: Struts Users Mailing List <[EMAIL PROTECTED]> >Subject: Re: 1.1 release date? >Date: Wed, 02 Oct 2002 10:54:52 -0500 > >Well said, David! > >While there is no date set, there are bugs to be squashed. If you find >yourself able to contribute patches to fix things that are wrong, you will >be able to "hurry" the final release ;-) These Jakarta folk don't release >on a time-line, but, instead, on a merit-line. When the software is >decided to be "worthy of the Jakarta name", it will be stamped final - not >before. > >Craig said at some point in the past how final releases are just >nightly >builds that "the developers think have been tested enough" (that's a >misquote, but you get the jist). > >Hop right in and put your heel down on a bug or two! That's the best >way >you can ensure a quicker release :-D > >If you're close to release and don't feel secure using the 1.1 >code-base, >by all means, use 1.0.2. If you're not so close to release, probably 1.1 >would be best. In the end, it's a judgement call only you can make ;-) >Have you actually tried a nightly build? There's a *lot* of added >functionality there. If you're on a container adhering to jsp >specification 1.2, the addition of the Struts-EL taglib could save you a >lot of hassle! > >David Graham wrote: > >>no >> >>>From: "Andy Kriger" <[EMAIL PROTECTED]> >>>Reply-To: "Struts Users Mailing List" >>><[EMAIL PROTECTED]> >>>To: "Struts Users Mailing List" <[EMAIL PROTECTED]> >>>Subject: 1.1 release date? >>>Date: Wed, 2 Oct 2002 11:20:08 -0400 >>> >>>I am interested in using Struts 1.1 for an upcoming project because >>>of >>>the >>>added features (especially validation). However, I don't want to use beta >>>software in a production release. Is there a target date for 1.1rel? >>> >>>thx >>>andy >> > >-- >Eddie Bush > > > > >-- >To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
