Comments on: Are Java web frameworks ready for building frontends? http://www.olympum.com/frameworks/are-java-web-frameworks-ready-for-building-frontends/ my random thoughts about the world wide web Tue, 06 Jan 2009 22:02:11 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Bruno http://www.olympum.com/frameworks/are-java-web-frameworks-ready-for-building-frontends/comment-page-1/#comment-1515 Bruno Sun, 20 Jul 2008 06:28:01 +0000 http://www.olympum.com/frameworks/are-java-web-frameworks-ready-for-building-frontends/#comment-1515 At some point I looked at <a href="http://www.olympum.com/frameworks/wicket-and-ejb3/" rel="nofollow">Wicket</a>, and found it to be the best of the Java presentation frameworks. I like component-based development, and Wicket (and Tapestry) both offer this. But there is a downside: memory. The automatic view-controller state management comes at a price, and I would <em>never</em> put Wicket on a publicly web facing website. In general, I would not put any statefull presentation framework for that matter. At some point I looked at Wicket, and found it to be the best of the Java presentation frameworks. I like component-based development, and Wicket (and Tapestry) both offer this. But there is a downside: memory. The automatic view-controller state management comes at a price, and I would never put Wicket on a publicly web facing website. In general, I would not put any statefull presentation framework for that matter.

]]> By: Wille http://www.olympum.com/frameworks/are-java-web-frameworks-ready-for-building-frontends/comment-page-1/#comment-1492 Wille Fri, 11 Jul 2008 16:21:04 +0000 http://www.olympum.com/frameworks/are-java-web-frameworks-ready-for-building-frontends/#comment-1492 Have you checked out Apache Wicket? To me, that was a return to being able to enjoy Java web development again, after avoiding it consciously for years. No jsp's, no xml configs, just plain html and plain (testable) Java. I have also written a framework on top of Wicket and JPA (inventively called "Wicket RAD" - http://sites.google.com/site/wicketrad/), which takes a lot of the heavy lifting away from standard webapp development: Just annotate a bean with JPA annotations, and Form annotations such as @TextField, @DropdownChoice etc, add a form-generator component to your page with your bean, and it will automatically generate a form that can persist or update the bean and backend data for you. I agree that JSP development is a pain, I wouldn't want to touch it with a barge pole, but the situation is quickly improving with new approaches, such as the ones I mentioned. Have you checked out Apache Wicket? To me, that was a return to being able to enjoy Java web development again, after avoiding it consciously for years. No jsp’s, no xml configs, just plain html and plain (testable) Java.

I have also written a framework on top of Wicket and JPA (inventively called “Wicket RAD” - http://sites.google.com/site/wicketrad/), which takes a lot of the heavy lifting away from standard webapp development:
Just annotate a bean with JPA annotations, and Form annotations such as @TextField, @DropdownChoice etc, add a form-generator component to your page with your bean, and it will automatically generate a form that can persist or update the bean and backend data for you.

I agree that JSP development is a pain, I wouldn’t want to touch it with a barge pole, but the situation is quickly improving with new approaches, such as the ones I mentioned.

]]>