Eelco, I appreciate your input- very objective answer!
-----Original Message----- From: Eelco Hillenius [mailto:[EMAIL PROTECTED] Sent: Friday, September 14, 2007 12:32 PM To: [email protected] Subject: Re: Wicket vs. JSF/Seam (The Dead Debate) On 9/14/07, William Hoover <[EMAIL PROTECTED]> wrote: > Our company is in the process of evaluating the feasibility in transitioning > our UI framework to Wicket. In doing so, I stumbled upon this article > http://ptrthomas.wordpress.com/2007/05/14/a-wicket-user-tries-jsf/ that does > a nice job of composing a simple side-by-side comparison of JSF and Wicket. > > We are currently using JSF/MyFaces/Tomahawk/Trinidad and have found it to be > quite a disappointment. I have personally been developing JSF applications > for several years and have encountered numerous issues with the framework > (not to mention the specification, components, etc.). I never understood how > JSF can be referred to as a true MVC framework when it maintains logic within > the view in the form of EL (thus the Wicket evaluation). > > With that said, I hear the argument from JSF/Seam developers (as seen in the > article mentioned above) that comparing Seam with Wicket is a better/fair > comparison. I have no experience with Seam and would like to know if there is > anyone using Wicket in this forum that has switched from Seam to Wicket that > could shed some light on the issue? You are refering to the JSF/ Seam combination, but mind you that while Seam started out as a fix for JSF, it nowadays tries to be an independent framework to sit in between UI frameworks and the typical business layer. For the latter purpose, we have some basic support for Seam, see http://chillenious.wordpress.com/2007/07/16/added-initial-seam-support-for-wicket/ As for the JSF/ Seam combination. I think the best thing you can do is play around with it yourself and see what you like best. My personal opinion is that though I can see that it is probably an improvement over regular JSF, I can imagine the programming model to be problematic for large projects, mainly because it depends on path expressions (global strings really) everywhere and I think this might be very hard to untangle when you do more complex stuff. It certainly is very different from Wicket's strategy of plain Java programming/ static typing etc. Eelco --------------------------------------------------------------------- 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]
