On 8/25/05, Paul Benedict <[EMAIL PROTECTED]> wrote: > The subject line asks it all. Is it true?
Once again? Man, you should have used [FRIDAY] prefix ;-) Tomorrow's Friday anyway. The short answer is the question: is servlet API dead? Do people still program to bare servlet API? > I hope we see a version 1.2.8 and a 1.3 soon, but I am > sorry to see all the innovation going into Spring > (YEAH!) and Shale (YAWN!), with no one really wanting > to continue growing the classic framework. There is Struts Ti (a lot of new stuff), my very own Struts Dialogs (just two action classes and a different mindset using existing codebase) http://struts.sourceforge.net/strutsdialogs, and other developments. > Is it viable to evolve Struts Classic into Shale, and > mix into the Shale source support for good old Struts? > I say it sounds like a good idea to me.... but I hope > there are better ideas than mine, or we'd all be in > trouble ;-) Currently Shale targets JSF as view technology, so unless Shale starts to support JSPs and Struts taglibs, Shale cannot be considered as evolution of Struts. > With that said, this is my opinion based on > observation of the amazing industry progression in the > MVC area. Would not call it amazing, seeing something like this: http://forum.springframework.org/viewtopic.php?t=4200 ;-)) Or are you talking about Microsoft, which adds first-class support for Front Controller pattern into ASP.NET 2.0? > I hope the Struts committers aren't burnt > out. I love Struts which is why I ask this tough > question. I hope I get some good news and be told I am > wrong :) The problem is, if you like Struts the way it is, you will not be happy with any radical changes, see DJ has split to Spring MVC. If you do not like Struts way of doing things and the word "Struts" make you puke, you will more likely jump to JSF/Shale/Tapestry/Wicket/etc right now. Basically, Struts is screwed ;-) I believe that the only way for further Struts Classic development is to use different approaches within current codebase. This is what I did with my Struts Dialogs. Basically, only one new action and a different request lifecycle. Struts is a wrapper over servlet API, kinda like MFC. I prefer it to stay this way, so I could use something relatively small and fast to build a small app (or if I wanted to put a lot of handcoding ;-) ). Struts cannot compete against JSF or Wicket or Tapestry in prototyping speed or in number of services it provides. On the other hand, what do you do if you want to use Front Controller framework? Switch to WebWork and Spring MVC, or to improve Struts? The only reason for Struts to improve is keeping Front controller aka web MVC as a cornerstone pattern. Michael. On 8/25/05, Paul Benedict <[EMAIL PROTECTED]> wrote: > The subject line asks it all. Is it true? > > I hope we see a version 1.2.8 and a 1.3 soon, but I am > sorry to see all the innovation going into Spring > (YEAH!) and Shale (YAWN!), with no one really wanting > to continue growing the classic framework. > > Is it viable to evolve Struts Classic into Shale, and > mix into the Shale source support for good old Struts? > I say it sounds like a good idea to me.... but I hope > there are better ideas than mine, or we'd all be in > trouble ;-) > > With that said, this is my opinion based on > observation of the amazing industry progression in the > MVC area. I hope the Struts committers aren't burnt > out. I love Struts which is why I ask this tough > question. I hope I get some good news and be told I am > wrong :) > > Thanks! > Paul > > > > ____________________________________________________ > Start your day with Yahoo! - make it your home page > http://www.yahoo.com/r/hs > > > --------------------------------------------------------------------- > 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]
