There have been a number of improvements, enhancements and bug fixes in this release. Described below Items listed in the later section are the most significant ones.
Table of Contents |
---|
Children Display |
---|
Geronimo distributions
cover the different downloads and certification status.
Feature enhancements and additions
Custom server assemblies
...
Lightweight server assemblies may be created that contain only the functional components required by your application(s). With previous versions of Geronimo, it was possible to create a custom server assembly as a build-time operation. It is now much simpler to create custom assemblies. Also, custom assemblies can be created that are tailor-built to the requirements of your applications.
The Geronimo project distributes 3 pre-defined server assemblies (an "assembly" is a binary distribution of Geronimo which is pre-configured and ready to run). The 3 pre-defined server assemblies distributed by the Geronimo project are:
{indent:2}
# Framework: contains only the Geronimo kernel with JMX and RMI Naming capability,
# Minimal: contains Web Container (e.g. JSP/Servlet), transaction, and connector,
# Java EE 5: contains all of the functionality required to be a fully Java EE 5 compliant.
{indent:1}
Geronimo now has Admin Console, Admin Command, and GEP support for generating custom assemblies. Build-time customization is still available, but is much simpler than in previous versions of Geronimo.
There are two modes of custom assembly creation:
{indent:2}
# Function centric -- Choose the functionality that suits your needs
# Application centric -- Let your applications define the contents of your server
{indent:1}
For more information on custom server assemblies, see [Extracting a server from an existing server|Plugin infrastructure#Extracting a server from an existing server.] and [Assembling a server using maven|Plugin infrastructure#Assembling a server using maven.]
Java SE 6 support
Geronimo v2.2 can be built on Java SE 6 and provide support to JAXB/JAX-WS version2 implementation, and its assemblies also supports Java 5 and 6 run-time environments.
Usability improvements
By embedding Web Containers like Tomcat/Jetty and JMS Server Active MQ, users can have a better experience when working with them. For example, user can use /var/activemq/conf/activemq.xml
to configure ActiveMQ and var/catalina/server.xml
to configure Tomcat directly. Other than the new consuming approach of those embedded modules, Geronimo also provides backwards compatibility, which means you can configure GBeans like you did in previous versions.
Console improvements
Plugin management
- By improving plugin converting method, user don't have to export a plugin for server assembly. In v2.2, a Geronimo configuration can be converted into a plugin directly. See Converting applications into plugins using the Administration Console for more details.
Save plan from Console directly
- By default, the resource adapters created via console wizards will be regarded as geronimo configuration, which means the module type of these resource adapters will be
car
. - By improving console wizards, the deployment plan was saved into repository together with deployed application.
Artifact management via Console
- Other than editing artifact aliases in a text editor, user can now update such information via Console. See substituting one module with another for the details.
- By adding a Remove button on the Repository portlet, user can now remove an already installed .jar file from repository.
Others
- JMS portlet improvements
- EJB portlet improvements
- Console accessibility improvements to comply with Section 508 Standards
- Custom server assembly user interface improvements
GShell improvements
In v2.2, new GShell commands are supported for remote GShell server management and server instance creation. See Geronimo GShell Commands for more details.
Reduce server footprint and start-up time
In Geronimo v2.2, we used Dojo 1.1.1 mini release instead of 0.4.3 legacy to reduce server footprint. And following console portlets are published as optional ones, user can enable them by installing plugins respectively.
- Debug View portlets as optional plugins
- Monitoring plugins as optional
- Plan Creator as optional plugins
Plugin profiles
Plugins are grouped by their function(category) in v2.2 and you can assemble a customized server more easily and quickly. A plugins group can be managed just as an individual plugin and you can also create your personal plugin profiles. see customizing server assemblies and Plugins Group for the details.
New GEP features and enhancements
The latest Geronimo Eclipse Plugin (GEP) provides compatibility support to previous versions of Geronimo server environment. The following new features and enhancements have been implemented in the latest GEP v2.2:
- GEP support for creating custom server assemblies. See Assembling a server using GEP for more details.
- GEP support for building plugins. See Converting applications into Geronimo plugins using GEP for more details.
- New datasource pool wizard for EAR application. See Using datasource pool wizard in GEP for more details.
- New security realm wizard for various applications. See Using security realm wizard in GEP for more details.
- Implementation of refactoring support in Eclipse. When performing a refactoring operation, you can preview all the changes to be carried out for the application, such as artifact ID and <context-root> element of a Web application.
- Profiling mode to start a Geronimo server in Eclipse. You can start a Geronimo server in profiling mode if Test and Performance Tools Platform Project is installed.
New server management features
Server farm/cluster management with dynamic members and improved deployment for off-line/new member scenarios, see Plugin based Farming for the details.
Geronimo Administration Console
There are a number of changes and enhancements in the administration console. Examine the table below to better understand the updates.
...
...
Common Console Actions
...
Server
...
Services
...
Applications
...
Security
...
Added
...
Information
...
Java System Info
Monitoring
...
Repository
...
Plugins
Plan Creator
...
Removed
...
Database Pools
Security Realms
JMS Resources
Memory & Uptime
...
JVM
...
Common Libs
...
...
Pluggable Administration Console
...
The Geronimo Administration Console is now component-based to mirror the flexible server capabilities. This allows the console to provide flexible administrative capabilities that mirror the capabilities of a custom server assembly.
In previous releases of Geronimo, the Administration Console was a monolithic implementation. It could only be used to manage a Java EE server assembly. It could not reasonably be used to manage alternate configurations of Geronimo (e.g. a Minimal server assembly).
Components update
...
Several components have been either updated or added since AG2.0. A components version table has been generated below in the [component version|#Component versions] section. The components that are bold are either newly introduced or upgraded from AG2.1 to AG 2.2.
Console enhancements
...
Several revisions and enhancements have been applied to the Administration console. Users may first notice the revision of links on the homepage of the Administration console. Certain navigation links in the left-pane have been renamed to better fit its functionality. A more detailed listing of the renamed links is provided in the table at the start of the "Geronimo Administrator Console".
Other enhancements include a [Monitoring] application and the Expert mode feature.
Expert mode
...
The expert mode feature is intended to allow advanced user more control of their processes running on the Apache Geronimo server. Typically, certain critical processes aren't accessible by users to modify. However, the expert mode option will enable users full control.
Deployment plans wizard
...
This new portlet, available in the Administration Console, assists users in making the deployment process easier. This wizard will guide users through a sequence of configurations to help facilitate the generation of the geronimo-web.xml file for *WAR* files.
The process of the Deployment Plan Wizard involves a series of questions to gather specific information to resolve dependency and references.
See [Plan Creator] for more details.
CA helper
...
The Certificate Authority (CA) portlet aids in providing the setup for a CA and issues certificates in correspondence to Certificate Signing Requests (CSR). The portlet also allows the initialization of the CA.
See the [Geronimo Administration Console] for further details.
GShell
...
GShell is a command-line processing environment that can be used for the execution of Geronimo commands. GShell is an extensible environment and includes support for editing, command history, and tab completion.
A number of Geronimo administrative commands have been implemented using GShell. The old administrative scripts (e.g. geronimo.sh/.bat, deploy.sh/bat, etc) are still available. Starting from Geronimo 2.2, GShell can be used for all command line scripts except client and simple start/stop server scenarios.
A set of new GShell commands are provided for managing plugin groups and creating multiple server instances, with farming and plugin profile support.
For documentation on base GShell capabilities, see [GShell].
Clustering Support
...
WADI can now be used to support the replication of HTTP Session state among multiple Geronimo servers. In previous releases of Geronimo, WADI could only be used along with the Jetty configuration of Geronimo. WADI can now be used with Tomcat configurations of Geronimo.
In addition to the new session replication support, applications can now be deployed to administratively-defined groups of Geronimo servers. This makes it easier to manage a single application across a number of Geronimo servers.
For additional information on the clustering capabilities of Geronimo, see ...
Monitoring Console Plugin
...
The monitoring console plugin provides monitoring support in the Geronimo Administration Console. The monitoring console can gather statistics and performance data from multiple Geronimo servers and graphically display this data to users.
For information about the monitoring console plugin, visit ...
Component versions
Below is a table describing the components included in both the previous and current releases.
Info |
---|
Note the bolded versions indicate components that are either newly introduced or upgraded from the preceding Geronimo release. |
Components | 2.0.2 | 2.1.1 | 2.1.2 | 2.2 |
---|---|---|---|---|
activeio-core | 3.0.0-incubator | 3.0.1 | 3.0.1 |
|
activemq-core | 4.1.1 | 4.1.2 | 4.1.2 |
|
activemq-ra | 4.1.1 | 4.1.2 | 4.1.2 |
|
annogen | 0.1.0 | 0.1.0 | 0.1.0 |
|
ant | NA | 1.7.0 | 1.7.0 | 1.7.1 |
ant-launcher | NA | 1.7.0 | 1.7.0-G589756 |
|
antlr | 2.7.2 | 2.7.5 | 2.7.5 |
|
asm | 2.2.3 | 2.2.3 | 2.2.3 |
|
asm-commons | 2.2.3 | 2.2.3 | 2.2.3 |
|
aspectjrt | NA | 1.5.2a | 1.5.3 |
|
axiom-api | 1.2.5 | 1.2.5 | 1.2.5 |
|
axiom-dom | 1.2.5 | 1.2.5 | 1.2.5 |
|
axiom-impl | 1.2.5 | 1.2.5 | 1.2.5 |
|
axis | 1.4 | 1.4 | 1.4 |
|
axis2-adb | 1.3 | 1.3 | 1.3 |
|
axis2-java2wsdl | 1.3 | 1.3 | 1.3 |
|
axis2-jaxws | 1.3 | 1.3 | 1.3 | 2.1 |
axis2-jaxws-api | 1.3 | 1.3 | 1.3 |
|
axis2-kernel | 1.3 | 1.3 | 1.3 |
|
axis2-metadata | 1.3 | 1.3 | 1.3 |
|
axis2-saaj | 1.3 | 1.3 | 1.3 |
|
backport-util-concurrent | 2.2 | 2.2 | 2.2 |
|
bcel | 5.2 | 5.2 | 5.2 |
|
castor | 1.0.5 | 1.0.5 | 1.0.5 |
|
catalina | 6.0.13-G543818 | 6.0.14-G614585 | 6.0.16-G652117 |
|
catalina-ha | 6.0.13 | 6.0.14 | 6.0.16 |
|
cglib-nodep | 2.1_3 | 2.1_3 | 2.1_3 |
|
commons-beansutils | 1.7.0 | 1.7.0 | 1.7.0 |
|
commons-beanutils | 1.6.1 | 1.7.0 | 1.7.0 |
|
commons-cli | 1.0 | 1.0 | 1.0 |
|
commons-codec | 1.3 | 1.3 | 1.3 |
|
commons-collections | 3.1 | 3.2 | 3.2 |
|
commons-digester | 1.8 | 1.8 | 1.8 |
|
commons-discovery | 0.4 | 0.4 | 0.4 |
|
commons-el | 1.0 | 1.0 | 1.0 |
|
commons-fileupload | 1.1.1 | 1.1.1 | 1.1.1 |
|
commons-httpclient | 3.0.1 | 3.0.1 | 3.0.1 |
|
commons-io | 1.1 | 1.2 | 1.2 |
|
commons-jexl | 1.1 | 1.1 | 1.1 |
|
commons-lang | 2.0 | 2.3 | 2.3 |
|
commons-logging | 1.0.4 | 1.0.4 | 1.0.4 |
|
commons-logging-api | NA | 1.0.4 | 1.0.4 |
|
commons-modeler | 2.0 | 2.0 | 2.0 |
|
commons-primitives | 20041207.202534 | 20041207.202534 | 20041207.202534 |
|
coyote | 6.0.13 | 6.0.14 | 6.0.16 |
|
cxf-api | 2.0.2-incubator | 2.0.2-incubator | 2.0.8 |
|
cxf-common-utilities | 2.0.2-incubator | 2.0.2-incubator | 2.0.8 |
|
cxf-metacode | 2.0.2-incubator | 2.0.2-incubator | 2.0.8 |
|
cxf-rt-bindings-soap | 2.0.2-incubator | 2.0.2-incubator | 2.0.8 |
|
cxf-rt-bindings-xml | 2.0.2-incubator | 2.0.2-incubator | 2.0.8 |
|
cxf-rt-core | 2.0.2-incubator | 2.0.2-incubator | 2.0.8 |
|
cxf-rt-databinding-jaxb | 2.0.2-incubator | 2.0.2-incubator | 2.0.8 |
|
cxf-rt-frontend-jaxws | 2.0.2-incubator | 2.0.2-incubator | 2.0.8 |
|
cxf-rt-frontend-simple | 2.0.2-incubator | 2.0.2-incubator | 2.0.8 |
|
cxf-rt-transports-http | 2.0.2-incubator | 2.0.2-incubator | 2.0.8 |
|
cxf-tools-common | 2.0.2-incubator | 2.0.2-incubator | 2.0.8 |
|
derby | 10.2.2.0 | 10.2.2.0 | 10.2.2.0 | 10.4.2.0 |
derbyclient | 10.2.2.0 | 10.2.2.0 | 10.2.2.0 |
|
derbynet | 10.2.2.0 | 10.2.2.0 | 10.2.2.0 |
|
derbytools | 10.2.2.0 | 10.2.2.0 | 10.2.2.0 |
|
dojo | 0.4.3 | 1.0.2 | 1.0.2 | 1.1.1 |
dojolegacy | NA | 0.4.3 | 0.4.3 |
|
dwr | 1.1.3 | 2.0.1 | 2.0.3 |
|
geronimo-activation_1.1_spec | 1.0 | 1.0.2 | 1.0.2 |
|
geronimo-annotation_1.0_spec | 1.1 | 1.1.1 | 1.1.1 |
|
geronimo-connector | 2.0.2 | 2.1.1 | 2.1.1 |
|
geronimo-ejb_3.0_spec | 1.0 | 1.0.1 | 1.0.1 |
|
geronimo-el_1.0_spec | 1.0 | 1.0.1 | 1.0.1 |
|
geronimo-interceptor_3.0_spec | 1.0 | 1.0.1 | 1.0.1 |
|
geronimo-j2ee-connector_1.5_spec | 1.1.1 | 2.0.0 | 2.0.0 |
|
geronimo-j2ee-management_1.1_spec | 1.0 | 1.0.1 | 1.0.1 |
|
geronimo-jacc_1.1_spec | 1.0 | 1.0.1 | 1.0.1 | 1.1-MR5 |
geronimo-javaee-deployment_1.1MR3_spec | 1.0 | 1.0 | 1.0 |
|
geronimo-javamail_1.4_mail | 1.2 | 1.4 | 1.5 |
|
geronimo-jaxr_1.0_spec | 1.1 | 2.0.0 | 2.0.0 |
|
geronimo-jaxrpc_1.1_spec | 1.1 | 2.0.0 | 2.0.0 |
|
geronimo-jms_1.1_spec | 1.1 | 1.1.1 | 1.1.1 |
|
geronimo-jpa_3.0_spec | 1.1 | 1.1.1 | 1.1.1 |
|
geronimo-jsp_2.1_spec | 1.0 | 1.0.1 | 1.0.1 |
|
geronimo-jta_1.1_spec | 1.1 | 1.1.1 | 1.1.1 |
|
geronimo-saaj_1.3_spec | NA | 1.0.0 | 1.0.0 |
|
geronimo-schema-j2ee_1.4 | 1.2 | 1.2 | 1.2 |
|
geronimo-schema-jee_5 | 1.1 | 1.1 | 1.1 |
|
geronimo-servlet_2.5_spec | 1.1 | 1.2 | 1.2 |
|
geronimo-stax-api_1.0_spec | 1.0 | 1.0.1 | 1.0.1 |
|
geronimo-transaction | 2.0.2 | 2.1.1 | 2.1.1 |
|
geronimo-ws-metadata_2.0_spec | 1.1.1 | 1.1.2 | 1.1.2 |
|
gmaven-mojo | NA | NA | 1.0-rc-2 |
|
gmaven-plugin | NA | NA | 1.0-rc-2 |
|
gmaven-runtime-default | NA | NA | 1.0-rc-2 |
|
groovy-all | NA | 1.1-rc-1 | NA |
|
groovy-all-minimal | NA | NA | 1.5.6 |
|
groovy-maven-plugin | 1.0-alpha-2 | 1.0-beta-2 | 1.0-beta-2 |
|
groovy-mojo-support | NA | 1.0-beta-2 | NA |
|
groovy-mojo-tools | NA | 1.0-beta-2 | NA |
|
gshell-ansi | NA | NA | 1.0-alpha-1 |
|
gshell-bootstrap | NA | 1.0-alpha-1 | 1.0-alpha-1 |
|
gshell-builtins | NA | 1.0-alpha-1 | 1.0-alpha-1 |
|
gshell-cli | NA | 1.0-alpha-1 | 1.0-alpha-1 |
|
gshell-clp | NA | NA | 1.0-alpha-1 |
|
gshell-command-api | NA | 1.0-alpha-1 | 1.0-alpha-1 |
|
gshell-common | NA | NA | 1.0-alpha-1 |
|
gshell-core | NA | 1.0-alpha-1 | 1.0-alpha-1 |
|
gshell-i18n | NA | NA | 1.0-alpha-1 |
|
gshell-embeddable | NA | 1.0-alpha-1 | NA |
|
gshell-maven-plugin | NA | 1.0-alpha-1 | 1.0-alpha-1 |
|
gshell-parser | NA | NA | 1.0-alpha-1 |
|
gshell-prefs | NA | NA | 1.0-alpha-1 |
|
gshell-remote-client | NA | 1.0-alpha-1 | 1.0-alpha-1 |
|
gshell-remote-common | NA | 1.0-alpha-1 | 1.0-alpha-1 |
|
gshell-remote-server | NA | 1.0-alpha-1 | 1.0-alpha-1 |
|
gshell-whisper | NA | 1.0-alpha-1 | 1.0-alpha-1 |
|
howl | 1.0.1-1 | 1.0.1-1 | 1.0.1-1 |
|
hsqldb | 1.7.2.2 | 1.7.2.2 | 1.7.2.2 |
|
httpcore | 4.0-alpha5 | 4.0-alpha5 | 4.0-alpha5 |
|
jasper | 6.0.13-G543818 | 6.0.14-G614585 | 6.0.16-G652117 |
|
jasper-el | 6.0.13 | 6.0.14 | 6.0.16 |
|
jasper-jdt | 6.0.13 | 6.0.14 | 6.0.16 |
|
jaxb-api | 2.0 | 2.0 | 2.0 |
|
jaxb-impl | 2.0.5 | 2.0.5 | 2.0.5 |
|
jaxb-xjc | 2.0.5 | 2.0.5 | 2.0.5 |
|
jaxb2-maven-plugin | NA | NA | 1.2 |
|
jaxen | 1.1-beta-10 | 1.1-beta-11 | 1.1-beta-11 |
|
jaxws-rt | 2.0 | 2.0 | 2.0 |
|
jaxws-tools | 2.0 | 2.0 | 2.0 |
|
jcl104-over-slf4j | NA | 1.4.3 | 1.4.3 | 1.5.5 |
jetty | 6.1.5 | 6.1.7 | 6.1.7 |
|
jetty-ajp | 6.1.5 | 6.1.7 | 6.1.7 |
|
jetty-sslengine | 6.1.5 | 6.1.7 | 6.1.7 |
|
jetty-util | 6.1.5 | 6.1.7 | 6.1.7 |
|
jline | 0.9.9 | 0.9.91 | 0.9.94 |
|
jspc-compiler-tomcat6 | 2.0-alpha-1 | 2.0-alpha-1 | 2.0-alpha-1 |
|
jspc-maven-plugin | 2.0-alpha-1-20070806 | 2.0-alpha-1-20070806 | 2.0-alpha-1-20070806 |
|
jstl | 1.2 | 1.2 | 1.2 |
|
juddi | 0.9rc4 | 0.9rc4 | 0.9rc4 |
|
juli | 6.0.13 | 6.0.14 | 6.0.16 |
|
juli-adapters | 6.0.13 | 6.0.14 | 6.0.16 |
|
junit | 3.8.1 | 3.8.1 | 3.8.1 |
|
log4j | 1.2.14 | 1.2.14 | 1.2.14 |
|
maven-assembly-plugin | NA | 2.2-beta-1 | 2.2-beta-1 |
|
maven-compiler-plugin | 1.5 | 1.5 | 2.0.2 |
|
maven-dependency-plugin | 2.0-alpha-4 | 2.0-alpha-4 | 2.0-alpha-4 |
|
maven-deploy-plugin | 2.3 | 2.3 | 2.3 |
|
maven-ear-plugin | 2.3 | 2.3 | 2.3 |
|
maven-enforcer-plugin | 1.0-alpha-2 | 1.0-alpha-3 | 1.0-alpha-3 |
|
maven-gpg-plugin | 1.0-alpha-3 | 1.0-alpha-3 | 1.0-alpha-3 |
|
maven-jar-plugin | 2.1 | 2.1 | 2.1 |
|
maven-javadoc-plugin | NA | 2.3 | 2.3 |
|
maven-plugin-plugin | NA | 2.3 | 2.3 |
|
maven-pmd-plugin | NA | 2.2 | 2.2 |
|
maven-rar-plugin | 2.2 | 2.2 | 2.2 |
|
maven-release-plugin | 2.0-beta-6 | 2.0-beta-6 | 2.0-beta-6 |
|
maven-remote-resources-plugin | NA | 1.0-alpha-5 | 1.0-alpha-5 |
|
maven-surefire-plugin | NA | 2.3 | 2.3 |
|
maven-war-plugin | 2.0.2 | 2.0.2 | 2.0.2 |
|
mina-core | NA | 1.1.5 | 1.1.5 |
|
mina-filter-ssl | NA | 1.1.5 | 1.1.5 |
|
mockobjects-core | 0.09 | 0.09 | 0.09 |
|
mockobjects-jdk1.4-j2ee1.3 | 0.09 | 0.09 | 0.09 |
|
myfaces-api | 1.2.0 | 1.2.2 | 1.2.3 |
|
myfaces-impl | 1.2.0 | 1.2.2 | 1.2.3 |
|
neethi | 2.0 | 2.0 | 2.0 |
|
ognl | 2.6.9 | 2.6.9 | 2.6.9 |
|
openejb-axis | 3.0 | 3.0 | 3.0 |
|
openejb-client | 3.0 | 3.0 | 3.0 |
|
openejb-core | 3.0 | 3.0 | 3.0 |
|
openejb-ejbd | 3.0 | 3.0 | 3.0 |
|
openejb-javaagent | 3.0 | 3.0 | 3.0 |
|
openejb-jee | 3.0 | 3.0 | 3.0 |
|
openejb-loader | 3.0 | 3.0 | 3.0 |
|
openejb-server | 3.0 | 3.0 | 3.0 |
|
openjpa | 1.0.0 | 1.0.2 | 1.0.2 |
|
openjpa-persistence-jdbc | 1.0.0 | 1.0.2 | 1.0.2 |
|
plexus-archiver | NA | 1.0-alpha-7 | 1.0-alpha-7 |
|
plexus-classworlds | NA | NA | 1.2-alpha-10 |
|
plexus-component-annotations | NA | NA | 1.0-alpha-1 |
|
plexus-component-api | NA | 1.0-alpha-15 | 1.0-alpha-32 |
|
plexus-container-default | NA | 1.0-alpha-9 | 1.0-alpha-32 |
|
plexus-utils | NA | 1.4.1 | 1.4.5 |
|
pluto-container | NA | 1.2.0-G601061 | 1.1.6-G643117 |
|
pluto-descriptor-api | NA | 1.2.0-G601061 | 1.1.6-G643117 |
|
pluto-descriptor-impl | NA | 1.2.0-G601061 | 1.1.6-G643117 |
|
pluto-portal-driver | NA | 1.2.0-G601061 | 1.1.6-G643117 |
|
pluto-portal-driver-impl | NA | 1.2.0-G601061 | 1.1.6-G643117 |
|
pluto-taglib | NA | 1.2.0-G601061 | 1.1.6-G643117 |
|
portlet-api | 1.0 | 1.0 | 1.0 |
|
regexp | 1.3 | 1.3 | 1.3 |
|
rmock | 2.0.0-rc-6 | 2.0.0-rc-6 | 2.0.0 |
|
saaj-impl | 1.3 | 1.3 | 1.3 |
|
scout | 1.0rc1 | 1.0rc1 | 1.0rc1 |
|
selenium-maven-plugin | 1.0-beta-1 | 1.0-beta-2 | 1.0-beta-3 |
|
serp | 1.11.0 | 1.11.0 | 1.11.0 |
|
shitty-maven-plugin | NA | 1.0-alpha-1 | 1.0-alpha-2 |
|
slf4j-api | 1.4.0 | 1.4.3 | 1.4.3 |
|
slf4j-gossip | NA | NA | 1.0-rc-2 |
|
slf4j-jcl | 1.4.0 | 1.4.3 | 1.4.3 |
|
slf4j-log4j12 | 1.4.0 | 1.4.3 | 1.4.3 |
|
slf4j-simple | NA | 1.4.3 | 1.4.3 |
|
spring | 2.0.5 | 2.0.5 | 2.0.5 |
|
spring-beans | 2.0.5 | 2.0.5 | 2.0.5 |
|
spring-context | 2.0.5 | 2.0.5 | 2.0.5 |
|
spring-core | 2.0.5 | 2.0.5 | 2.0.5 |
|
spring-web | NA | 2.0.5 | 2.0.5 |
|
sql-maven-plugin | 1.0 | 1.0 | 1.0 |
|
swizzle-stream | 1.0.1 | 1.0.1 | 1.0.1 |
|
tranql-connector-db2-xa | 1.1 | 1.2 | 1.2 |
|
tranql-connector-derby-client-local | 1.4 | 1.4 | 1.4 |
|
tranql-connector-derby-client-xa | 1.4 | 1.4 | 1.4 |
|
tranql-connector-derby-embed-local | 1.4 | 1.4 | 1.4 |
|
tranql-connector-derby-embed-xa | 1.4 | 1.4 | 1.4 |
|
tranql-connector-mysql-local | 1.1 | 1.2 | 1.2 |
|
tranql-connector-mysql-xa | 1.1 | 1.2 | 1.2 |
|
tranql-connector-oracle-local | 1.3 | 1.3 | 1.3 |
|
tranql-connector-oracle-xa | 1.3 | 1.3 | 1.3 |
|
tranql-connector-postgresql-local | 1.1 | 1.1 | 1.1 |
|
tranql-connector-postgresql-xa | 1.1 | 1.1 | 1.1 |
|
tranql-connector-ra | 1.4 | 1.4 | 1.4 |
|
tribes | 6.0.13 | 6.0.14 | 6.0.16 |
|
wadi-aop | NA | 2.0-M10 | 2.0 |
|
wadi-core | 2.0-M5 | 2.0-M10 | 2.0 |
|
wadi-group | 2.0-M5 | 2.0-M10 | 2.0 |
|
wadi-tribes | 2.0-M5 | 2.0-M10 | 2.0 |
|
wsdl4j | 1.6.1 | 1.6.1 | 1.6.2 |
|
wstx-asl | 3.2.1 | 3.2.1 | 3.2.1 |
|
xalan | 2.7.0 | 2.7.0 | 2.7.0 |
|
xbean-finder | 3.2 | 3.3 | 3.3 |
|
xbean-naming | 3.2 | 3.3 | 3.3 |
|
xbean-reflect | 3.2 | 3.3 | 3.3 |
|
xercesImpl | 2.8.1 | 2.8.1 | 2.8.1 |
|
xml-resolver | 1.1 | 1.1 | 1.1 |
|
xmlbeans | 2.3.0 | 2.3.0 | 2.3.0 |
|
xmlbeans-maven-plugin | 2.3.1 | 2.3.1 | 2.3.1 |
|
XmlSchema | 1.3.1 | 1.3.1 | 1.3.1 |
|
xpp3 | 1.1.3.3 | 1.1.3.4.O | 1.1.3.4.O |
|
xstream | 1.1.3 | 1.2.2 | 1.2.2 |
|
yoko-core | 1.0-incubating-r557035 | 1.0-r646887 | 1.0 |
|
yoko-rmi-impl | 1.0-incubating-r557035 | 1.0-r646887 | 1.0 |
|
yoko-rmi-spec | 1.0-incubating-r557035 | 1.0-r646887 | 1.0 |
|
yoko-spec-corba | 1.0-incubating-r557035 | 1.0-r646887 | 1.0 |
|
Configuration changes
Review the configuration changes in a 2.1 server.
- the new
config.xml
- plugins interaction
- defaults
- config-substitution
Backwards compatibility
Geronimo plugin metadata (META-INF/geronimo-plugin.xml) and plugin catalog (geronimo-plugins.xml) content is incompatible with previous versions (1.x and 2.0.x). If you have a geronimo plugin for an earlier version of Geronimo you will have to manually convert it to the new schema. The best way to do this is to build the plugin with maven and use the car-maven-plugin to generate the metadata. See Plugin infrastructure
Security configuration of run-as and default identities is incompatible with geronimo 1.x versions. If you use run-as roles or default identities you will have to manually modify your geronimo plans to the new mechanism. See Configuring run-as and Default Subjects, and principal-role mapping
Review backward compatibility issues.
Global JNDI for resources and admin objects
Starting in Geronimo 2.0 all ejbs are bound in global jndi using a configurable pattern. Starting in Geronimo 2.1 all resources such as datasources and admin objects (e.g. jms queues and topics) are also bound in global jndi using a pattern configurable in var/config/config-substitutions.properties. See JNDI