Trails is a domain driven development framework for Java that aims to bring some of the excellent ideas of Ruby on Rails to the Java platform. By developing a POJO domain model with some annotations, it is possible to get a fully working Spring/Hibernate/Tapestry application without custom development. Trails does this without any source code generation and all screens are fully customizable as needed. As well, Trails provides other features such as validation, role based security and I18N.

Waffle is a Java Web framework that allows for pojo-based actions. Dependency injection support is built in. Waffle does NOT have a proprietary templating language nor does it require any XML configuration files. Waffle apps are easy to write and test. We - the developers of Waffle (http://waffle.sf.net) and VRaptor (http://vraptor.org) - would like to join forces and first port Waffle to Codehaus (renaming it to use org.codehaus.waffle package) and gradually port features from VRaptor in order to create a larger and more consolidated community around a lean web application framework which honours the least-common-denominator principle. We greatly appreciate the Haus community and will abide by the Haus Manifesto. We hope that the new effort will further consolidate the already strong Haus branding as an incubator of high-quality commercially-friendly Java-based libraries. Mauro, Mike, Paul (for Waffle community) Guiherme, Paulo (for VRaptor community)

openXMA is a framework and a set of development tools (Eclipse plug-ins) for implementing Java thin, rich client applications. Basically, openXMA programs are web applications where client side Java code, based on SWT, will be downloaded and executed automatically. So look-and-feel like typical OS native rich clients is provided. Client code is cached locally, client and server halfs are communicating highly optimized via http. Please have a look to the project site http://openxma.codehaus.org/ to get more information.

qixweb was born by refactoring a few XP projects from the ground up. Its essential elements are: 1. an abstraction of node, each representing a page in a browser; each node is attached to some piece of the domain, but the domain is kept separated and clean ==> nodes may be connected directly to each other or via commands, which constitutes an abstraction of navigation of the entire webapp 2. an abstraction of command as action that will change the domain, producing a new node ==> ie: these commands may be used to wrap easily Prevayler commands 3. an abstraction of browser, url and link that keep nodes & commands well separated in turn from servlets and container aspects ==> it is therefore possible to test all the dynamic navigation logic server side without working with html, http or containers 4. an abstraction of response handler and renderer that enables browser to use template engines like Velocity on one side and that opens the world of multichannel applications on the other side