<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/platform.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar/13069857?origin\x3dhttp://rcampoamor.blogspot.com', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

Saturday, January 21, 2006

The Value of JSF for Web Development

TheServerSide has a long and heated discussion on the value of using JavaServer Faces for web application development. This was sparked by a blog post with the somewhat incendiary title of "JSF: The 7-Layer Burrito I Won't Eat Again".

My question is: why does every discussion about JSF usually end with someone bringing up Tapestry rather than dealing with the merits and liabilities of JSF?

technorati tags: ,

posted by rich at 10:11 AM

0 Comments:

Post a Comment

<< Home