Finally, the new website is ready to go live on the Internets. it is a complete rewrite of the existing architecture, sporting full CMS control over files and images, a lot of new features and a more intuitive structure.

The new site is implemented using the great Apache Wicket framework. Never heard of it? Here are a few quick facts about it:

• EASY (SIMPLE / CONSISTENT / OBVIOUS)
  • POJO-centric
  • All code written in Java ala Swing
  • Minimize "conceptual surface area"
  • Avoid overuse of XML configuration files
  • Fully solve back button problem
  • Easy to create bookmarkable pages
  • Maximum type safety and compile-time problem diagnosis
  • Maximum diagnosis of run-time problems
  • Minimum reliance on special tools
  • Components, containers and conventions should be consistent
• REUSABLE
  • Components written in Wicket should be fully reusable
  • Reusable components should be easily distributed in ordinary JAR files
• NON-INTRUSIVE
  • HTML or other markup not polluted with programming semantics
  • Only one simple tagging construct in markup
  • Compatible with any ordinary HTML editor
  • Easy for graphics designers to recognize and avoid framework tagging
  • Easy to add tagging back to HTML if designers accidentally remove it
• SAFE
  • Code is secure by default
  • Only explicitly bookmarkable links can expose state in the page or URL
  • All logic in Java with maximum type safety
  • Easy to integrate with Java security
• EFFICIENT / SCALABLE
  • Efficient and lightweight, but not at the expense of other goals
  • Clustering through sticky sessions preferred
  • Clustering via session replication is easy to accomplish and easy to tune by working with detachable models.
• COMPLETE
  • The Wicket team is committed to deliver a feature complete, ready-to-use framework for developing Java web applications. The core framework was written and contributed by the author of this introduction, Jonathan Locke. The current team consists of a group of experienced programmers, some of which were active on some of the other frameworks stated above, and all of which have extensive experience building large scale Java web applications. We eat our own dogfood, and will thus work on Wicket from a framework user's perspective.