...

The following list briefly describes major changes and enhanced functionality from the previous release of Apache Geronimo.

Repository

...

The config-sotre has been removed and it has been consolidated into a single repository directory structure.

Deployment

• Deployment plans
  Deployment The plans have been updated to support versioning, configId has been totaly removed and replaced with a whole new structure as illustrated in the following example.

  Code Block
  xml xml borderStyle solid
  <dep:moduleId> <dep:groupId>geronimo</dep:groupId> <dep:artifactId>ApplicationId</dep:artifactId> <dep:version>1.1</dep:version> <dep:type>war</dep:type> </dep:moduleId>

  Refer to Deployment plans for details.

• ReDeploy command for existing deployed applications.
  You no longer need to stop, uninstall, install and start an application you want to redeploy. This commands allows you to redeploy installed applications matching the moduleId.

• New hot deploy for compressed jars.

• In Place deployment for exploded J2EE modules.
  Allows you to deploy an application from a directory external to Geronimo's directory structure, you can point the deployer tool to the directory where you develop the application.

• Offline deployer available as a tech-preview.

• Cached login settings for deploy tool.
  Allows you to store user name as password so you don't have to type it every time you run the commands.

Tools and commands

As a consequence of changing the configId, the commands will now take moduleId as the paramenter instead of configId.

Schemas

The XML schemas have also changed to reflect the configID to moduleId change. geronimo-config-1.1.xsd

...

has been replaced with geronimo-module-1.1.xsd

• configId -> moduleId
Enhanced SMTP support in JavaMail.

• Shared library for users.

• Keystore configuration

New features

Anchor
newFeatures newFeatures

...