No offense meant! I've been (and continue to be) very grateful to Struts. I was referring specifically to Struts 1.1, not 1.x.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 29, 2005 4:46 PM > To: user@struts.apache.org; [EMAIL PROTECTED] > Subject: RE: How does Shale affect my Struts development > > Plus, it's not accurate to call Struts 1.x "a codebase which > is no longer being maintained." > > > -----Original Message----- > > From: Frank W. Zammetti [mailto:[EMAIL PROTECTED] > > Sent: Thursday, December 29, 2005 3:53 PM > > To: Struts Users Mailing List > > Subject: Re: How does Shale affect my Struts development > > > > > > Hi Daniel, > > > > I think upgrading to 1.2.x *is* compelling, if you decide > you want to > > stay on the Action-oriented path. There have been enough fixes and > > enhancements since 1.1 to warrant that upgrade. I suggest reading > > through the history to see what has been done. > > > > The whole Struts vs. Shale decision comes down to how you want (or > > need) to architect your applications. There is a huge number of > > reasons to choose one over the other, and I seriously doubt I could > > enumerate them all, so I would suggest reading up on the > > component-oriented architectures out there, since you > already know the > > action-oriented paradigm, and see if it better suits your > needs. Many > > people find that it does, but just as many find that it > doesn't. That > > may well change over time, but it's reality (as far as I'm aware) > > today. > > > > Whatever you do, my advice is to *NOT* choose the component-based > > paradigm simply because you hear it's the "future of web > development", > > or that it's just "obviously better". I'm not going to > debate whether > > those things might be true or not, I'm simply pointing out that > > neither, in my mind at least, are good enough reasons to go > one way or > > the other. > > There is a lot of hype, and you need to cut through it and really > > see what is underneath. If you find merit in it, then by > all means go > > for it! Like I said, many people believe it's a > no-brainer, and you > > may agree in the end. Just don't agree because anyone > tells you that > > you should :) > > > > Frank > > > > Daniel Blumenthal wrote: > > > Actually, not to start that holy war, but I'm in the middle of > > > refactoring my Struts 1.1 app, and am trying to decide > > whether there's > > > any compelling reason to upgrade to either 1.2.x, or Shale. > > > > > > Struts 1.1 has certainly been just fine - and unless > there's a good > > > reason (important security upgrade, must-have feature, > significant > > > speed improvements, etc.) I'm happy staying with it. But I > > feel like > > > I should understand why I'm staying with a codebase which > > is no longer > > > being maintained, rather than doing it through ignorance. > > > > > > Any thoughts? > > > > > > Daniel > > > > > > > > >>-----Original Message----- > > >>From: Alexandre Poitras [mailto:[EMAIL PROTECTED] > > >>Sent: Thursday, December 29, 2005 10:01 AM > > >>To: Struts Users Mailing List > > >>Subject: Re: How does Shale affect my Struts development > > >> > > >>Bernhard is totally right. The choice you are facing is > wheter you > > >>want to go for now on with components-based frameworks (JSF/Shale, > > >>Tapestry) or a typical action-based framework (Struts/Webwork). > > >>Struts is supporting the two choices for the moment and I > think it's > > >>great! > > >> > > >>But don't ask for the pro and cons of each approach here > or you'll > > >>start a holy war! Just kidding ;) > > >> > > >>On 12/29/05, Bernhard Slominski > > >><[EMAIL PROTECTED]> wrote: > > >> > > >>>Hi Jim, > > >>> > > >>>don't make the following mistake: > > >>>"I use Struts but I want to move on, so I have to use Shale!" > > >>> > > >>>Shale is build ON TOP of JSF, so to understand the > benefit of Shale > > >>>you have to know JSF. > > >>>So the first question to ask yourself: > > >>>"Do I want to move to JSF or is Struts just fine for me?" > > >>>When you decided to move to JSF or to at least take a > > >> > > >>closer look at > > >> > > >>>it then after being familiar with JSF you can look at Shale > > >> > > >>and see if > > >> > > >>>that's the right technology for you. > > >>>I guess in your case you seem to be fine with Struts, so > > >> > > >>just stay with it! > > >> > > >>>Bernhard > > >>> > > >>> > > >>>>-----Ursprüngliche Nachricht----- > > >>>>Von: Jim Reynolds [mailto:[EMAIL PROTECTED] > > >>>>Gesendet: Donnerstag, 29. Dezember 2005 15:10 > > >>>>An: user@struts.apache.org > > >>>>Betreff: How does Shale affect my Struts development > > >>>> > > >>>> > > >>>>First off, a little background. I have started using > the 'Struts' > > >>>>framework about 1 year ago. I have created three apps, > and all is > > >>>>moving along pretty well with the Struts and model 2 > > >> > > >>approach. I am > > >> > > >>>>just starting to use more design patterns for my business > > >> > > >>logic, etc. > > >> > > >>>>Anyway, as you may be aware I frequent this list, and try > > >> > > >>to keep up > > >> > > >>>>with what is going on with the Struts project. > > >>>> > > >>>>I am noticing a lot of 'Shale' discussion, and I have > > >> > > >>just finished > > >> > > >>>>reading the link here > > >> > > >><http://struts.apache.org/struts-shale/> and > > >> > > >>>>franky, I am not sure what Shale brings to the table > that is not > > >>>>already included with Struts? > > >>>> > > >>>>I guess, the reason for this post is, I was hoping > possibly there > > >>>>are people out there who understand this Struts/Shale and > > >> > > >>could tell > > >> > > >>>>me how to get started, and what the gain is. Whether the best > > >>>>approach is to build a simple Struts app and convert > it, or what > > >>>>steps I need to take in order to be prepared and keep my > > >> > > >>skill set > > >> > > >>>>where it needs to be. > > >>>> > > >>>>Regards > > >>>> > > >>>> > > >> > > > >>-------------------------------------------------------------------- > > >> > > >>>>- 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] > > >>> > > >>> > > >> > > >> > > >>-- > > >>Alexandre Poitras > > >>Québec, Canada > > >> > > >>------------------------------------------------------------ > > --------- > > >>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] > > > > > > > > > > > > > > > > -- > > Frank W. Zammetti > > Founder and Chief Software Architect > > Omnytex Technologies > > http://www.omnytex.com > > AIM: fzammetti > > Yahoo: fzammetti > > MSN: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
