Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

Anchortoptop

Some changes have been introduced in this new relase that affects the configuration and deployment plans of existing installations. In this section we will focus on highlighting those differences, how to apply the necessary changes as well as some migration aid tools when available.

...

If the application uses resource reference in 1.1, resource references need to be resolvable in the set of ancestors of your module. In other words, your application has to depend on the rar deployment.

Example:

...

...

Without the dependency specified, you may run into the following error upon deployment of your application:

...

...

2) Manually convert the derby jar dependencies to system-datasource:

If your 1.0 database connection pool plan has the following as dependencies:

...

...

The upgrader tool will convert them to:

...

However, this loads a second copy of derby in a second classloader, and you will hit the following error when you run your application:

...

Instead you need a car dependency on system-datasource so you are sharing it's copy of derby.

...

...

Using the administration console

When you deploy an application using the administration console the portlet will automatically detect a 1.0 plan and invoke the upgrader tool described above to provide a 1.1 plan that you can save locally, make adjustments to if necessary, and then use to deploy your application. The console currently only provides this functionality for external plan files.