Apache Wicket
From Wikipedia, the free encyclopedia
![]() |
|
| Developer(s) | Apache Software Foundation |
|---|---|
| Stable release | 1.3.6 / 2009-05-03 |
| Preview release | 1.4-rc6 / 2009-07-04 |
| Written in | Java |
| Operating system | Cross-platform |
| Development status | Active |
| 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. It was originally written by Jonathan Locke in Spring of 2005. Version 1.0 was released in June 2005. It graduated into an Apache top-level project in June 2007.[1]
Contents |
[edit] Rationale
Traditional MVC frameworks work in terms of whole requests and whole pages. In each request cycle, the incoming request is mapped to a method on a controller object, which then generates the outgoing response in its entirety, usually by pulling data out of a model to populate a view written in specialised template markup. This keeps the application's flow-of-control simple and clear, but can make code reuse in the controller difficult.
[edit] Design
Wicket, on the other hand, is closely patterned after stateful GUI frameworks such as Swing. Wicket applications are trees of components, which use listener delegates to react to HTTP requests against links and forms in the same way that Swing components react to mouse and keystroke events.
Wicket uses plain XHTML for templating (which enforces a clear separation of presentation and business logic and allows templates to be edited with conventional WYSIWYG design tools[2]). Each component is bound to a named element in the XHTML and becomes responsible for rendering that element in the final output. 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. The framework does not have knowledge of how components interact with their models, which are treated as opaque objects automatically serialized and persisted between requests. 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.
[edit] Example
A Hello World Wicket application, with four files:
- HelloWorld.html
- The XHTML template.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:wicket="http://wicket.apache.org/dtds.data/wicket-xhtml1.3-strict.dtd" xml:lang="en" lang="en"> <body> <span wicket:id="message" id="message">Message goes here</span> </body> </html>
- HelloWorld.java
- The page component that will be bound to the template. It, in turn, binds a child component (the Label component named "message").
package org.wikipedia.wicket; import org.apache.wicket.markup.html.WebPage; import org.apache.wicket.markup.html.basic.Label; public class HelloWorld extends WebPage { /** * Constructor */ public HelloWorld() { add(new Label("message", "Hello World!")); } }
- HelloWorldApplication.java
- The main application class, which routes requests for the homepage to the HelloWorld page component.
package org.wikipedia.wicket; import org.apache.wicket.protocol.http.WebApplication; public class HelloWorldApplication extends WebApplication { /** * Constructor. */ public HelloWorldApplication() { } /** * @see org.apache.wicket.Application#getHomePage() */ public Class getHomePage() { return HelloWorld.class; } }
- web.xml
- The servlet application definition, which installs Wicket as the default handler for the servlet and arranges for HelloWorldApplication to be instantiated at startup.
<?xml version="1.0" encoding="UTF-8"?> <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5"> <web-app> <display-name>Wicket Examples</display-name> <filter> <filter-name>HelloWorldApplication</filter-name> <filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class> <init-param> <param-name>applicationClassName</param-name> <param-value>org.wikipedia.wicket.HelloWorldApplication</param-value> </init-param> </filter> <filter-mapping> <filter-name>HelloWorldApplication</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> </web-app>
[edit] References
- ^ Dashorst, Martijn (2007-07-20). "Wicket graduates from Apache Incubation". http://martijndashorst.com/blog/2007/06/20/3-2-1. Retrieved on 2008-03-07..
- ^ Carleton, Daniel (2007-10-12). "Java Web Development the Wicket Way". DevX. http://www.devx.com/Java/Article/35620. Retrieved on 2008-03-07..
[edit] Bibliography
- Dashorst, Martijn; Hillenius, Eelco (September 15, 2008), Wicket in Action, Manning, pp. 392, ISBN 1932394982, http://www.manning.com/dashorst/
- Tong, Kent (June 20, 2008), Enjoying Web Development with Wicket, TipTec Development, pp. 412, ISBN 978-99937-929-0-1, http://www.agileskills2.org/EWDW/
- Gurumurthy, Karthik (September 7, 2006), Pro Wicket, Apress, pp. 328, ISBN 1-59059-722-2, http://www.apress.com/book/view/9781590597224
[edit] See also
[edit] External links
[edit] Introductory articles
- Wicket: A simplified framework for building and testing dynamic Web pages
- 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)
[edit] Blogs
[edit] 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
|
|||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||


