Return-Path: Delivered-To: apmail-cocoon-cvs-archive@www.apache.org Received: (qmail 99339 invoked from network); 14 Oct 2003 21:41:19 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 14 Oct 2003 21:41:19 -0000 Received: (qmail 98179 invoked by uid 500); 14 Oct 2003 21:41:06 -0000 Delivered-To: apmail-cocoon-cvs-archive@cocoon.apache.org Received: (qmail 98136 invoked by uid 500); 14 Oct 2003 21:41:05 -0000 Mailing-List: contact cvs-help@cocoon.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@cocoon.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list cvs@cocoon.apache.org Received: (qmail 98108 invoked by uid 500); 14 Oct 2003 21:41:05 -0000 Delivered-To: apmail-cocoon-2.1-cvs@apache.org Received: (qmail 98033 invoked from network); 14 Oct 2003 21:41:04 -0000 Received: from unknown (HELO minotaur.apache.org) (209.237.227.194) by daedalus.apache.org with SMTP; 14 Oct 2003 21:41:04 -0000 Received: (qmail 99202 invoked by uid 1672); 14 Oct 2003 21:41:16 -0000 Date: 14 Oct 2003 21:41:16 -0000 Message-ID: <20031014214116.99201.qmail@minotaur.apache.org> From: joerg@apache.org To: cocoon-2.1-cvs@apache.org Subject: cvs commit: cocoon-2.1/src/documentation/xdocs/installing updating.xml X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N joerg 2003/10/14 14:41:16 Modified: src/documentation/xdocs/installing updating.xml Log: inconsistences reported by Lars Huttar fixed Revision Changes Path 1.21 +22 -51 cocoon-2.1/src/documentation/xdocs/installing/updating.xml Index: updating.xml =================================================================== RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/installing/updating.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- updating.xml 12 Oct 2003 13:31:55 -0000 1.20 +++ updating.xml 14 Oct 2003 21:41:16 -0000 1.21 @@ -14,24 +14,21 @@ -

Please take your time to read this document completely before trying to upgrade from - a Cocoon 2.0.x installation to 2.1 (or above).

- This is a brief discussion of the changes between the latest official release @released.version@ - and the current development version of Apache Cocoon. - You only need this information if you are updating an existing Cocoon installation, or - if you want to know what is going on in the development of Cocoon. + Please take your time to read this document completely before trying to upgrade from + a Cocoon 2.0.x installation to 2.1 (or above). You can also read it if you want to + know what was going on in the development of Cocoon.

The Cocoon team took great care in making this new version as compatible as possible. However, in order to achieve even more flexibility, usability and performance, the internal architecure of Cocoon has been improved. Due to these - improvements it has not been possible to be compatible in every little detail. + improvements it has not been possible to be compatible in every little detail. If you follow the instructions of document closely, however, you should be able to quickly upgrade your Cocoon 2.0.x installation.

- The Cocoon team has developed many Avalon components that are not specific to Cocoon + The Cocoon team has developed many Avalon components that are not specific to Cocoon and therefore have been donated to the Avalon Excalibur project and moved out of Cocoon. This has led to some configuration changes which are also described in this document. @@ -82,8 +79,6 @@ component. If the type attribute is omitted, the default configuration from the map:components section is used.

The SAXConnectors have been removed, so if you upgrade manually you have to remove - the sax-connectors configuration from cocoon.xconf.

So it's not that bad, despite incompatible changes in the Cocoon code there is little to do to update your Cocoon installation.

@@ -94,32 +89,34 @@

Relative paths in FOP serializer's <user-config> are now resolved relatively - to the directory that contains the sitemap.

Relative paths in FOP serializer's <user-config> are now resolved + relatively to the directory that contains the sitemap.

All Cocoon URIs are supported too.

- In order to have consistent namespaces, some transformers - and generators (listed below) use new namespaces. If you use any of these components, you will - need to use the new namespaces. + In order to have consistent namespaces, some transformers and generators + (listed below) use new namespaces. If you use any of these components, you + will need to use the new namespaces.

RequestGenerator changed its namespace from http://xml.apache.org/cocoon/requestgenerator/2.0 to - http://apache.org/cocoon/request/2.0. +

RequestGenerator changed its namespace from + http://xml.apache.org/cocoon/requestgenerator/2.0 to + http://apache.org/cocoon/request/2.0.

The I18nTransformer changed its namespace from - http://apache.org/cocoon/i18n/2.0 to http://apache.org/cocoon/i18n/2.1

The I18nTransformer supports both + http://apache.org/cocoon/i18n/2.0 and + http://apache.org/cocoon/i18n/2.1 namespace.

Due to some interface changes in the Cocoon logging components, custom java - components (generators,transformers or actions for example) compiled for Cocoon 2.0.x will not run - under Cocoon 2.1 unless recompiled.

+ components (generators, transformers or actions for example) compiled for Cocoon + 2.0.x will not run under Cocoon 2.1 unless recompiled.

It's also advisable to change your implementations from using Loggable to LogEnabled when it comes to logging in your components.

@@ -128,8 +125,6 @@

The Cocoon architecture has changed significantly. However, great care has been taken to preserve backwards compatibility. - This effort has been successful except for - one change which shouldn't affect anybody (see below).

In order to reflect the new version, the version information in the cocoon.xconf @@ -137,6 +132,8 @@

To update cocoon.xconf, we recommend that you start with the new cocoon.xconf from V2.1 and incorporate your changes in it, instead of trying to migrate your old configuration file.

The SAXConnectors have been removed, so if you upgrade manually you have to remove + the sax-connectors configuration from cocoon.xconf.

The SourceResolver is now an Avalon component @@ -144,33 +141,7 @@ The package name of the component is org.apache.excalibur.source.

- There are some issues related to JDK 1.4 -

- +

There are some issues related to JDK 1.4.

Another serious issue is the presence of the Xalan and Xerces package in the JDK 1.4. For general information on this please read the @@ -259,7 +230,7 @@

The class name for file upload has changed from org.apache.cocoon.components.request.multipart.FilePart to org.apache.cocoon.servlet.multipart.Part, and the getFilePath() has been renamed - Part.getUploadName(). + Part.getUploadName().