Wicket and Guice

Are you sick of XML? I sure am. While I really like Spring Framework, I am sick of all the XML. Writing unit tests is hard enough, but how do you test XML? Some might argue that it isn't really code and doesn't need testing. Some might be wrong. What I want is a way to write code WITHOUT XML.

Two interesting projects have caught my attention:
* Wicket
* Guice

---

Wicket - Home: "Welcome to Wicket

With proper mark-up/logic separation, a POJO data model, and a refreshing lack of XML, Wicket makes developing web-apps in Java simple and enjoyable again. Swap the boilerplate, complex debugging and brittle code for powerful, reusable components written with plain Java and HTML.

* Check the feature list
* Read some Wicket buzz or some Wicket blogs
* Find out why you should use Wicket
* Check out some examples and see them in live action
* Download Wicket 1.2.6

Wicket is released under the Apache License, Version 2.0 ."

---

Guice wholly embraces annotations and generics, thereby enabling you to wire together and test objects with less effort than ever before. Annotations finally free you from error-prone, refactoring-adverse string identifiers.

In a nutshell:

* Guice empowers dependency injection.
* Guice cures tight coupling.
* Guice enables simpler and faster testing at all levels.
* Guice reduces boilerplate code.
* Guice is type safe.
* Guice externalizes configuration when appropriate.
* Guice lets you compose your application of components which are truly independent.
* Guice reports error messages as if they will be read by human beings.
* Guice is the anti-static.
* Guice is small and very fast.