Wicket is a Java Web application framework implementing simplicity, separation of concerns, and ease of development. Wicket pages can be mocked up, previewed, and later revised using standard WYSIWYG HTML design tools. Dynamic content processing and form handling is all handled in Java code using a component model backed by POJO data beans that can easily be persisted using your favourite technology.
Echomine Feridian is an easy-to-use Java API that gives you quick and easy access to the XMPP network used in IM services such as Google Talk. The API allows you to communicate with Jabber/XMPP servers for sending and receiving instant messages, presence management, and custom extensions to the XMPP protocol.
dao-zero is a tiny Java bean used to reduce the source of a persistence tier based on Spring's iBatis support. The usual way to use iBatis in Spring is to write code and invoke the iBatis API explicitly. dao-zero invokes the iBatis API for the developer automatically, without the need to write implementation code. It will implement DAO interfaces automatically and invoke iBatis SQL mapped statements for you. You can use it to replace your DAO bean class directly.
The Spring Rich Client Project (RCP) is a sub-project of the Spring Framework. Spring-RCP's mission is to provide an elegant way to build highly-configurable, GUI-standards-following rich-client applications faster by leveraging the Spring Framework. It also provides a rich library of UI factories and support classes. Its initial focus is on providing support for Swing applications, but a goal of Spring-RCP is to be view agnostic as much as possible.
JCons provides a library that bring color to your Java console. The Java console gives no methods to change the foreground or background color. With help of this library, one can make error messages red and success messages green, for example. Most Unix terminals can deal with ESC sequences, so they are used to make the Java console colorful.
VRaptor 2 is a Web-based MVC and IOC framework based on many frameworks and ideas (Seam, Stripes, Webwork, Hibernate Annotations, etc). It makes full use of Java 5 Annotations. It favors convention over configuration, because configuration in XML/properties/annotations is always easy to make mistakes and repetitive (aka copy and paste in many places). This framework uses a more imperative approach, instead of having many XML files to configure lifecycle and other properties. Most of the settings go inside plain Java objects (POJO), so the team knows exactly what is going on and where.