Wicket Article Series
I started an article series about Wicket on InformIT.com last week and thus far I have become very encouraged. The thing that I like about Wicket is that it is simple to move from an HTML mockup to a working application - add a few wicket:id attributes to the HTML tags to which you want to add dynamic content and then build logic in a corresponding Java component to generate that dynamic content. This brings up another point, it is very natural for me, as a Java developer, to build content inside a Java class and to work with Java objects rather than to build that same presentation logic using a tag library.
For example:
HelloWicket.html
HelloWicket.java
The question that I have for anyone reading this is with regards to Wicket integration with Spring and Hibernate - any experience? I read through the Spring and Hibernate chapter of Wicket In Action tonight and it looks feasible, but still not as elegant as the Spring MVC or Struts 2 integration. But if I can work through a clean solution, I may very well have found my next favorite web framework
But I'll hold off my formal recommendation of Wicket until I run some performance tets - its session memory usage looks like it could become problematic if not properly managed.
So please chime in if you have any Wicket experience and have any insight that might make the article series better - like why you like Wicket and what cool things make it better than its competition.
For example:
HelloWicket.html
<html>
<body>
<h1 wicket:id="message">This is my message</h1>
</body>
</html>
HelloWicket.java
public class MyPage extends WebPage {In the article that will publish this week, I build a more substantial example of a simple content management system that I originally built using Spring MVC for JavaWorld, that illustrates how to use the ListView as a repeater to display multiple articles in the "repository" (ok, it's hard coded inside the application for now), how to handle links, and how to navigate from the HomePage to an Article page. The next week I'll complete the content that I built for the Spring MVC example by building and handling the form submission.
public MyPage() {
add( new Label( "message", "Hello, Wicket!" );
}
}
The question that I have for anyone reading this is with regards to Wicket integration with Spring and Hibernate - any experience? I read through the Spring and Hibernate chapter of Wicket In Action tonight and it looks feasible, but still not as elegant as the Spring MVC or Struts 2 integration. But if I can work through a clean solution, I may very well have found my next favorite web framework
But I'll hold off my formal recommendation of Wicket until I run some performance tets - its session memory usage looks like it could become problematic if not properly managed.So please chime in if you have any Wicket experience and have any insight that might make the article series better - like why you like Wicket and what cool things make it better than its competition.
Wicket is really session heavy.It maintains a lot of data in the session.The memory consumption increases drastically as the application is navigated/used.
Reply to this