Apache Wicket web applications with just Java.ppt

Apache Wicket: web applications with just Java Xavier Hanin JavaZone ‘07 Who is Xavier Hanin Independent Java Consultant Customers Open Source Agenda What is Wicket Core concepts of Wicket Developing a custom component QA Wicket in a Nutshell Open Source (Apache Software Foundation) Component based Pure Java + Pure HTML Simple Enthusiastic community What is Wicket? The technology: enabling component-oriented, programmatic manipulation of markup The mission: bringing object oriented programming to the web application view layer The reward: have a fun job and be good friends with your manager again Achieving these goals through Keeping simple things simple Utilizing an object-oriented component model where components are truly self contained Re-applying the Model View Controller pattern on components instead of requests, with models as first class citizens Having a clean separation of concerns between HTML and Java Achieving these goals through Providing transparent, fully automated state management Keeping configuration needs to the minimum No more XML! Making using creating custom components easier than any framework out there Component versus ‘traditional’ Traditional Struts, WebWork, Spring MVC, etc. Proven for web A lot of web developers available Components JSF, Wicket, Tapestry, etc. Traditional model for UI development on thick clients A lot of developers available Features Page composition panels, borders and markup inheritance Excellent localization and style support template and resource loading (_be.html, .xml) localized models (e.g. for labels) sophisticated resource bundle lookup (composition inheritance hierarchy) automatic client capabilities detection Features Integration Spring Guice Hibernate JasperReports OSGi Fancy components sortable, filterable, pageable, data aware tables date picker, rich text editor, Google Maps tabbed panel, navigation, tree, wizard Features State management type safe sessions clustering support back button support