Geronimo 2.2 can use the profiles implemented with EE 6 through custom Geronimo implementations called assemblies. In previous versions, creating customized Geronimo runtimes was largely a build-time operation. With assemblies in version 2.2, users can export a new custom server image from a running Geronimo server. Assemblies allow several different approaches for applying plugins.
Another focus of the Apache Geronimo project is faster startup. 2.2 features a more compact server with improved cluster support using WADI. There is broader tool support thanks to extended GShell functionality. Also included are some new plugins for Apache OpenJPA 2.0 and Apache ActiveMQ's administration console.
Geronimo 2.2 has updated integrations with these Apache projects:
- OpenEJB 3.1
- Axis 2 1.5
- Derby 10.5
- Camel 2.0
- OpenJPA 1.2
- ActiveMQ 5.3
- Tomcat 6.0.2
- CXF 2.1
And these third party projects:
- Dojo 1.4
- Jetty 7
The project committers say that migrating from Tomcat to Geronimo in version 2.2 is probably easier than it was before. Switching from the commons-logging library to the slf4j library another significant change in Geronimo. The sfl4j library resolves several issues with various logging product versions. Log4J is still used in the standard implementation.
Geronimo 2.2 is a big step in making the project fully Java EE 6 compliant. JAX-B 2.1, JAX-WS 2.1, JAX-RS 0.8, JPA 2.0 and parts of EJB 3.1 are already supported in Geronimo 2.2. Java EE 6 certification with Sun is the primary goal for Geronimo 3.0. Committers on the project plan to drop Java SE 5 support by version 3.0 and require SE 6. Another major goal for Geronimo 3.0 is OSGi support through Apache Karaf or Felix.