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 :-)

It's happened again: once in a while I must install the latest version of Eclipse IDE on my laptop, for various reasons (check some plugin, see how things look there, and so on).
Hence, one more time, I come to Eclipse website, spend some nice time finding the right version for me, then download, uncompress, start. When it prompts for workspace location, an ancient image comes in front of my eyes and I start remembering Amiga workbench and its drawers...

Syncope recently gained official support for Glassfish 3.1.1: since the JPA layer did - again recently - move to Apache OpenJPA, we faced some issues when trying to deploy Syncope - as OpenJPA-powered web application - to Glassfish.

When writing Java code relying on Spring and JPA, you may eventually come to the need of some scheduling; since Quartz is by far the reference in this field, you think you will solve all of your problems by reading the appropriate page on Spring docs. Wrong, at least if you need some Spring goodies like @Autowired and @Transactional.

Syncope needs a new workflow engine, for many good reasons: here's why I've started playing around with Activiti.
Activiti looks really interesting because of features and Apache 2.0 license; moreover, its spicy story makes it even more attractive.

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.

I've recently come up to a very wicked problem in Syncope, and a saving blog post pointed me in the right direction:
Getting your persistence access right when working with background jobs in Spring can be tricky.