There are lots of ways of documenting RESTful APIs in Java: just google a bit and you will find the nice Enunciate and Swagger, for example. Such approachs, however, are often quite invasive and hardly customizable. Many providers - like as Apache CXF - are able to dynamically generate a WADL representation out of JAX-RS annotated classes: such XML representation can be easily put into an XSLT transformation in order to obtain some end-user REST documentation.
Will you ever think to deploy a webapp based on the most diffuse and popular Apache Cocoon version (2.1) onto the most recent Apache Tomcat? Well, despite of the fact that the former reached its widest spread when the the latter's major version was 3, 4 or 5 at most, it is actually possible. Only, completely undocumented :-)
I recently presented some aspects of the renewed Apache Cocoon power through its latest (and not yet completed) release, 3.0. Today I am going to present some features of the Hippo Cocoon Toolkit, whose aim is to provide an alternative, Cocoon 3.0 based, toolkit for building front-end web sites while relying upon Hippo CMS and Repository.
Some articles are already around about Apache Cocoon 3.0, a deep rewrite of an Apache project that is bringing to the community innovative concepts since 1998. To be honest, the latest release is slowly approaching to a stable level, especially if compared to the wide spread and appreciation that 2.x series used to have - and still has, to a certain extent - all around the world.
After very good news I have reported before, this morning I have received a very pleasant e-mail saying that since today I have been accepted as member of the Apache Cocoon PMC. Wow, I am still astonished by all this new stuff :-)