Comments on: Improving JavaServer Faces by dumping JSP http://almaer.com/blog/improving-javaserver-faces-by-dumping-jsp blogging about life, the universe, and everything tech Fri, 04 May 2012 14:57:05 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: Howard M. Lewis Ship http://almaer.com/blog/improving-javaserver-faces-by-dumping-jsp/comment-page-1#comment-3736 Howard M. Lewis Ship Thu, 10 Jun 2004 23:24:26 +0000 http://almaer.com/blog2/improving-javaserver-faces-by-dumping-jsp#comment-3736 Mike --- good assesment, but that's what Tapestry does; it maps from coarse grained HTTP requests to method invocations. It doesn't do anything particularily magical, and it doesn't require client-side JavaScript to make anything work. It doesn't use or mimic Swing, but it takes on the flavor of GUI development. Jason -- No Book For You! Actually, drop me an e-mail with your snail mail address. Mike — good assesment, but that’s what Tapestry does; it maps from coarse grained HTTP requests to method invocations. It doesn’t do anything particularily magical, and it doesn’t require client-side JavaScript to make anything work. It doesn’t use or mimic Swing, but it takes on the flavor of GUI development.

Jason — No Book For You! Actually, drop me an e-mail with your snail mail address.

]]> By: Mike Spille http://almaer.com/blog/improving-javaserver-faces-by-dumping-jsp/comment-page-1#comment-3735 Mike Spille Thu, 10 Jun 2004 21:33:44 +0000 http://almaer.com/blog2/improving-javaserver-faces-by-dumping-jsp#comment-3735 I agree with Jason on this one. Taking a component model too far adds too much complexity to what's fundamentally a pretty easy task. A big part of the problem is that things like JSF try to model a web page as a very fine grained event-driven GUI - and web pages don't really work that way. The model doesn't match the reality, and developers end up programming to a rich-GUI paradigm when the underlying physical reality is a fairly dumb HTML/DHTML combination. If you're programming to fine grained events, and your actual infrastructure is ultra-coarse request-response, you're just asking for trouble. I agree with Jason on this one. Taking a component model too far adds too much complexity to what’s fundamentally a pretty easy task. A big part of the problem is that things like JSF try to model a web page as a very fine grained event-driven GUI – and web pages don’t really work that way. The model doesn’t match the reality, and developers end up programming to a rich-GUI paradigm when the underlying physical reality is a fairly dumb HTML/DHTML combination. If you’re programming to fine grained events, and your actual infrastructure is ultra-coarse request-response, you’re just asking for trouble.

]]> By: jsf_user http://almaer.com/blog/improving-javaserver-faces-by-dumping-jsp/comment-page-1#comment-3734 jsf_user Thu, 10 Jun 2004 11:10:03 +0000 http://almaer.com/blog2/improving-javaserver-faces-by-dumping-jsp#comment-3734 JSF: Future Tapestry: Past. Webwork: Jason the troll. JSF: Future
Tapestry: Past.
Webwork: Jason the troll.

]]> By: Jason Carreira http://almaer.com/blog/improving-javaserver-faces-by-dumping-jsp/comment-page-1#comment-3733 Jason Carreira Thu, 10 Jun 2004 11:00:21 +0000 http://almaer.com/blog2/improving-javaserver-faces-by-dumping-jsp#comment-3733 Blah... I'm not sold on either one... Web pages just aren't that complicated, and when you start trying to make them that complicated, you should really be using something else. Blah… I’m not sold on either one… Web pages just aren’t that complicated, and when you start trying to make them that complicated, you should really be using something else.

]]>