Aochuqu Answers are needed! It is a new project Wicket in SourceForge, which is developed by Sun's Swing Ui Engineering Group, tried to express the web ui with a unique and simple way.
As with TapeStry, Wicket is also embedded in HTML to a label for special naming rules. Unlike TapeStry, it is very simple (as easy as the dirt on the body), there is not too complex HTML syntax. Without an XML configuration file, Wicket is a simple component model similar to Swing.
Wicket can be integrated with Hibernate. There are one or two IDE plugins, this framework is even more suitable for JSP and JSF, and Wicket is more suitable in a large environment away from traditional J2EE development habits. Finally, let's talk about an open source project based on the Apache software license agreement.
Access Wicket Home:
http://wicket.sourceforge.net/
Some people compare Wicket and Tapestry:
Your point is correct, Tapestry is more mature than wicket. Now you can apply TapeStry to the actual project. The Wicket is applied to the project, at least until 1.0 official version of the month after months.
I think the true advantage of Wicket is that more than Tapestry can solve more problems encountered in the Web UI. In fact, when I was very excited with Wicket, I was still in hardworking TapeStry. Maybe I have learned something very slow, but I don't want a framework to read too much books and documents. I like it all. Like the goalkeeper standing on the top of the arc, Wicket can use a simple method and the right to solve the problem.
(Please note! Quote, transfer this article to note: rosen Jiang and the source:
http://blog.9cbs.net/rosen
)
