Comments on: Goliath meet David: Seam/JSF versus Wicket http://wicketinaction.com/2009/01/goliath-meet-david-seamjsf-versus-wicket/ A comprehensive guide for Java developers building Wicket-based web applications Fri, 15 Jan 2010 04:01:26 +0100 http://wordpress.org/?v=2.9.1 hourly 1 By: nepoez http://wicketinaction.com/2009/01/goliath-meet-david-seamjsf-versus-wicket/comment-page-1/#comment-659 nepoez Wed, 13 Jan 2010 20:45:30 +0000 http://wicketinaction.com/?p=330#comment-659 Seam is not JSF. Seam can used for integration and can work with JSF and wicket. I don't think JSF/Seam can be compared to Wicket. JSF vs Wicket yes. Seam is not JSF. Seam can used for integration and can work with JSF and wicket.

I don’t think JSF/Seam can be compared to Wicket. JSF vs Wicket yes.

]]> By: Hussein Baghdadi http://wicketinaction.com/2009/01/goliath-meet-david-seamjsf-versus-wicket/comment-page-1/#comment-378 Hussein Baghdadi Thu, 15 Jan 2009 14:49:29 +0000 http://wicketinaction.com/?p=330#comment-378 Cool! A very logical comparison and a very amazing Wicket :) Seam isn't that bad guys, I think it is so powerful integration framework. Cool!
A very logical comparison and a very amazing Wicket :)
Seam isn’t that bad guys, I think it is so powerful integration framework.

]]> By: Jonathan Locke http://wicketinaction.com/2009/01/goliath-meet-david-seamjsf-versus-wicket/comment-page-1/#comment-377 Jonathan Locke Wed, 14 Jan 2009 16:28:23 +0000 http://wicketinaction.com/?p=330#comment-377 Not to mention: simpler, more flexible, more object-oriented, more secure, more agile (refactorable), etc. Of course, I might be biased. ;-) Not to mention: simpler, more flexible, more object-oriented, more secure, more agile (refactorable), etc. Of course, I might be biased. ;-)

]]>