 |
|
| Developed by | Apache Software Foundation |
|---|---|
| Latest release | 1.3.5 / 18 October 2008 |
| Preview release | 1.4-rc1 / 13 November 2008 |
| Written in | Java |
| OS | Cross-platform |
| Type | Web application framework |
| License | Apache License 2.0 |
| Website | http://wicket.apache.org |
Apache Wicket is a lightweight component-based web application framework for the Java programming language conceptually similar to JavaServer Faces and Tapestry. Version 1.0 was released in June 2005. It graduated into an Apache top-level project in June 2007.[1]
Wicket uses plain XHTML for templating, to enforce a clearer separation of presentation and logic and to allow templates to be edited with conventional WYSIWYG design tools.[2]
In traditional MVC frameworks, the controller works in terms of whole requests and whole pages and is responsible for pulling data out of the model to populate the view. Wicket components, on the other hand, are patterned after widgets in GUI frameworks such as Swing. Wicket components use listener delegates to react to GETs and POSTs against links and forms in the same way that Swing does to react to mouse and keystroke events on widgets.
The common idiom is to instantiate a tree of components, each of which is then bound to a named element in the XHTML. The component then becomes responsible for rendering that element in the markup. The page is simply the top-level containing component and is paired with exactly one XHTML template. Reuseable parts of pages may be abstracted into components called panels, which can then be pulled whole into pages or other panels with a special tag.
Each component is backed by its own model, which represents the state of the component and is automatically serialized and persisted between requests. Model objects are treated as opaque by the framework and how components interact with their models are their own business. More complex models, however, may be made detachable and provide hooks to arrange their own storage and restoration at the beginning and end of each request cycle. Wicket does not mandate any particular object-persistence or ORM layer, so applications often use some combination of Hibernate objects, EJB beans or POJOs as models.
Contents |
References
- ^ Dashorst, Martijn (2007-07-20). "Wicket graduates from Apache Incubation". Retrieved on 2008-03-07..
- ^ Carleton, Daniel (2007-10-12). "Java Web Development the Wicket Way". DevX. Retrieved on 2008-03-07..
Books
- Gurumurthy, Karthik (2006), Pro Wicket, Apress, ISBN 1-59059-722-2
- Tong, Kent (2007), Enjoying Web Development with Wicket, TipTec Development, ISBN 978-99937-929-0-1
- Dashorst, Martijn; Hillenius, Eelco (2008), Wicket in Action, Manning, ISBN 1932394982
See also
External links
Introductory articles
- A First Look at the Wicket Framework
- The Server Side discussion on Wicket 1.0
- Tim Boudreau's Blog
- Kickstart Wicket in NetBeans IDE 6.1
- The Server Side discussion
- Javalobby interview with Martijn Dashorst (project chairman)
Blogs
Documentation
- Reusable components and patterns for Wicket
- Site that has live demos and a repository of components
- Wiki with how-tos, a manual and more
Miscellaneous Links
|
||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||
No comments have been added.
