1 / 20

Apache Wicket

Apache Wicket. Java Web Application Framework. What is Wicket?. Web Application Framework Component-Component-based Framework Wicket 1.4 is Java 1.5+ compliant. Where does Wicket fit?. Request / Response. JSP Request / Response. Model 2 (MVC). Struts, Spring MVC, Stripes.

herschel
Download Presentation

Apache Wicket

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Apache Wicket Java Web Application Framework

  2. What is Wicket? • Web Application Framework • Component-Component-based Framework • Wicket 1.4 is Java 1.5+ compliant

  3. Where does Wicket fit?

  4. Request / Response • JSP Request / Response

  5. Model 2 (MVC) • Struts, Spring MVC, Stripes

  6. Advantages of R/R • Rendering views is generally quite fast • Development can leverage existing tag libraries • Recruiting developers may be easier • Modern implementations have good support for DI and IoC frameworks

  7. Disadvantages of R/R • Controller implementations must explicitly • consider multiple concurrent users and threads • Controllers generally work literally in terms ofHTTP requests and responses • Controllers often explicitly manage state • Not strictlyObject Oriented • The programming model is skewed

  8. The Impedance Mismatch The Programming Model • Programming in Java - do we regularly focus on how the JVM manages object instances and variables? • Generally, website development requires an understanding of the HTTP protocol. • IE: manually managing state within and across requests forces front end handlers to be protocol specific.

  9. What if ... ? • What if we considered a page ... a Page? • What if we considered a button ... a Button? • And upon clicking a button, handled an onClick event? • What if web-development resembled Swing or event-drivendevelopment? • What kind of framework could possibly enable this?!

  10. Enter ... Wicket • Component-based framework • Instead of creating a controller, servlet or action class ... create a Page • Place components on said Page and define how each component reacts to user input • •Build the Page in Java to manage HTML page elements ... not the other way around

  11. Web App Config • web.xml

  12. Wicket Config • WicketApplication.java

  13. General Structure • Layout the element hierarchy • Style the elements • Markup (HTML’s Role) • Code (Java’s Role) • Properties Files

  14. Hello World • Markup • Java

  15. Result

  16. Forms (HTML) • Markup

  17. Forms (Java) • Java

  18. Component Family

  19. Advantages • POJO-centric • Avoid overuse of XML configuration files • Fully solve back button problem • Easy to create bookmarkable pages • Reusability • Easy to integrate with Java security • Compatible with any ordinary HTML editor

  20. Wicket Resources Wicket Links • http://wicket.apache.org/ • http://wicketstuff.org/ • http://cwiki.apache.org/WICKET/ Wicket Books • Wicket in Action (Manning) • Pro Wicket (Apress)

More Related