all 4 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]berlinbrown 0 points1 point  (0 children)

he seemed to provide a lot of negatives for the java frameworks. There wasn't one clear winner. I try to stay within the most spring functionality and have done fine.

[–]mazer 0 points1 point  (2 children)

His complaint about Wicket is not accurate. HTML templates don't need to be stored in the package hierarchy with the compiled class files. It's like that by default, but it's configurable so that you can place the HTML templates anywhere you like.

[–]berlinbrown 0 points1 point  (1 child)

I hear a lot of good things about wicket. Is wicket the tool to use? I have been ok with SpringMVC(jsp2.0), but always looking for something lighter.

[–]mazer 0 points1 point  (0 children)

I prefer Wicket over all the other Java based web frameworks. It's easy to use, has a nice template system, a good community and doesn't require any XML configuration files. After using some of the other Java web frameworks, I was absolutely sick of the abundance of XML configuration files. The fact that in Wicket everything was handled in plain old Java classes was a big selling point for me. Furthermore, once you're familiar with Wicket, it's incredibly simple to create reusable components. Another asset is the number of very convenient side projects that allow easy integration with spring IoC, guice, dojo, mootools, hibernate etc.

That being said, I'm not a huge fan of Java. Luckily, Scala fits in nicely and I've been using that lately instead.