Code Ronin covering the Web Framework Smackdown
From the blogging search after the Smackdown, I’ve found the Code Ronin to have blogged about it, and the following quotes made me trigger:
Out of those presented, the only ones I can see us migrating to are JSF, Tapestry, and Shale. Why not Wicket and WebWork? Well, while Wicket sounds delightful, it sounds really different, and as for WebWork, I have to agree with Craig.
Glad to hear that Wicket sounds delightful, but considering your next statement on JSF:
Using JSF will be easy. The biggest con is that the tags it presents are VERY GUI oriented, designed to replace HTML in the JSPs. That’s great for developers, but not so great for the web integrators at my workplace who like to code their own HTML and JavaScript, thank you very much. Still, my boss spoke of visual beans two years back, and that’s what JSF is.
I REALLY ENCOURAGE you to take an interest in Wicket as we allow the web designers to design and developers develop nearly independently. Wicket has a pure HTML nature fulfilling your requirement to allow webdesigners to design the pages.
I invite you to check it out and see whether you like it. It is too early to dismiss it based on ‘it sounds really different’. I attended several JSF sessions on JavaOne, sat through both ‘Tapestry in Action’ and ‘WebWork’ presentations, and I dare to say: Wicket is far more easy to grok than the other component based frameworks, and I might add: the current myriad of MVC frameworks.
July 4th, 2005 at 3:26 pm
Yeah, the word “different” was really inapporpriate, sorry.
What I meant to say is that it would take time for us to learn it and adjust the “way we work”, more so than say JSF (which we can kinda use with Struts), Shale (legacy) and Tapestry (which some favour cause it is “mature”).
Still, like I said, first item of business is to rewrite our logic into POJOs, so our choice of framework will be more open. I will probably revisit Wicket at that time
July 4th, 2005 at 3:53 pm
Whether you are going to work with JSF, Tapestry or Wicket, your programming paradigm is going to shift anyway. That is the ‘unlearning curve’ that Howard Lewis Ship is talking about, and that is the same for each framework you mentioned (apart from WebWork, but just like you I agree with David Geary here).
Moving your business logic into the POJO’s is always a good thing, when working with either JSF, Wicket or Tapestry. But I doubt that Struts will enable you to leverage your POJO’s too much.