...to be "politically" correct, "Application Framework", but I'm referring to 
the portion of the framework that addresses the UI.

-----Original Message-----
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Friday, September 14, 2007 12:22 PM
To: [email protected]
Subject: Re: Wicket vs. JSF/Seam (The Dead Debate)


I didnt know Seam was a UI framework...

-Igor


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?
>
> Thanks in advance!
>
>
> ---------------------------------------------------------------------
> 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]

Reply via email to