cvs commit: cocoon-2.1/src/documentation/xdocs/installing updating.xml
cziegeler2003/07/02 00:21:04 Modified:src/documentation/xdocs/installing updating.xml Log: Enhancing update doc Revision ChangesPath 1.14 +22 -0 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.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- updating.xml 30 Jun 2003 14:23:57 - 1.13 +++ updating.xml 2 Jul 2003 07:21:03 - 1.14 @@ -239,5 +239,27 @@ /p /s2 /s1 + s1 title=Components from the scratchpad +pCocoon 2.0.x had some components in the scratchpad area that have now moved into + the main trunk as blocks. With this move some things have changed. +/p +s2 title=Session, Authentication and Portal + pThe session framework (sunShine), the authentication framework (sunRise) + and the portal framework (sunSpot) are now blocks (session-fw, authentication-fw + and portal-fw). + /p + pThe emsunShine transformer/em has been renamed to emsession transformer/em. +All sitemap components starting with emsunrise-/em have been changed to +start now with emauth-/em. The emsunrise-auth/em action has been +renamed to emauth-protect/em. + /p + p + The transformer namespace has changed from emhttp://cocoon.apache.org/sunshine/1.0/em + to emhttp://apache.org/cocoon/session/1.0/em and the context names have changed + from emsunshine/em to emsession/em and from emsunrise/em to + emauthentication/em. + /p +/s2 + /s1 /body /document
cvs commit: cocoon-2.1/src/documentation/xdocs/installing updating.xml
cziegeler2003/06/30 05:59:26 Modified:src/documentation/xdocs/installing updating.xml Log: Enhancing update doc Revision ChangesPath 1.11 +71 -60cocoon-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.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- updating.xml 21 Jun 2003 05:24:55 - 1.10 +++ updating.xml 30 Jun 2003 12:59:26 - 1.11 @@ -15,26 +15,83 @@ s1 title=Updating Cocoon pPlease take your time to read this document completely before trying to upgrade from - a Cocoon 2.0.x version to 2.1 (or above)./p + a Cocoon 2.0.x installation to 2.1 (or above)./p p 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. /p - p - The Cocoon team has developed many Avalon components which are not specific to Cocoon and have - been donated to the Avalon Excalibur project and moved out - of Cocoon. This has led to some configuration changes which are described - in this document. + pThe 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. +But if you follow this document closely and follow the instructions listed here, +you should have running an upgraded version very quickly. /p p -The internal architecture of cocoon has also been improved to give more flexibility, usability and performance. + 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. /p /s1 s1 title=Sitemap pThere are some changes in the sitemap and in the configuration of some components in the sitemap./p + s2 title=Pipelines configuration in the sitemap + p + The configuration of the pipelines has moved from cocoon.xconf to the sitemap. + To update your installation, you have to remove the event-pipeline and stream-pipeline section + from your cocoon.xconf and add the codemap:pipes/code section to the codemap:components/code section + of your sitemap. You can find the pipelines components definition in the sample + main sitemap of Cocoon. Here is an example: + /p + source![CDATA[ +map:sitemap + map:components + ... + map:pipes default=caching + map:pipe name=caching +src=org.apache.cocoon.components.pipeline.impl.CachingProcessingPipeline/ + map:pipe name=noncaching +src=org.apache.cocoon.components.pipeline.impl.NonCachingProcessingPipeline/ + /map:pipes + /map:components + ... +/map:sitemap + ]]/source + pYou can choose these different pipeline implementations + in the codemap:pipeline/code section by specifying their codetype/code attribute: + /p + source![CDATA[ +map:sitemap + ... + map:pipelines + map:pipeline type=noncaching + map:match pattern=welcome + ... + /map:match +.. + /map:pipeline + /map:pipelines +/map:sitemap + ]]/source + pThis is similar to choosing the type of a generator or any other sitemap + component. If the type attribute is omitted, the default configuration from the codemap:components/code + section is used. + /p + pThe SAXConnectors have been removed, so if you upgrade manually you have to remove +the emsax-connectors/em configuration from emcocoon.xconf/em./p + pSo it's not that bad, despite incompatible changes in the Cocoon code there is + little to do to update your Cocoon installation./p +/s2 + s2 title=Individual configuration of pipelines +pThe sitemap now provides individual configuration of codemap:pipeline/code sections. + You can now define one pipeline using caching, another one not using + caching at all and a third one using a different caching implementation, for example. +/p + /s2 s2 title=FOP Serializer pRelative paths in FOP serializer's lt;user-configgt; are now resolved relatively to the directory that contains the
cvs commit: cocoon-2.1/src/documentation/xdocs/installing updating.xml
cziegeler2003/06/30 06:17:43 Modified:src/documentation/xdocs/installing updating.xml Log: Enhancing update doc Revision ChangesPath 1.12 +7 -1 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.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- updating.xml 30 Jun 2003 12:59:26 - 1.11 +++ updating.xml 30 Jun 2003 13:17:43 - 1.12 @@ -203,7 +203,13 @@ s2 title=Stores pThe Store and StoreJanitor components and implementations have been moved to Avalon Excalibur./p -pTODO:Changes in cocoon.xconf.../p +pTo make upgrading easier, the class attributes of the store janitor + component has been removed in the emcocoon.xconf/em as the class names have changed. + The emcache-transient/em and emcache-persistent/em components do + not exists anymore, so remove any reference from the cocoon.xconf. Instead + the empersistent-store/em and emtransient-store/em components + fulfil their tasks. +/p pIn general the package names changed from emorg.apache.cocoon.components.store/em to emorg.apache.excalibur.store/em (and emorg.apache.excalibur.store.impl/em). So if you have custom java code using these components, you have to change
cvs commit: cocoon-2.1/src/documentation/xdocs/installing updating.xml
bdelacretaz2003/06/30 07:23:57 Modified:src/documentation/xdocs/installing updating.xml Log: minor typos and style changes Revision ChangesPath 1.13 +10 -10cocoon-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.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- updating.xml 30 Jun 2003 13:17:43 - 1.12 +++ updating.xml 30 Jun 2003 14:23:57 - 1.13 @@ -22,12 +22,13 @@ 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. /p - pThe Cocoon team took great care in making this new version as compatible as -possible. However in order to achieve even more flexibility, usability and + p +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. -But if you follow this document closely and follow the instructions listed here, -you should have running an upgraded version very quickly. +If you follow the instructions of document closely, however, +you should be able to quickly upgrade your Cocoon 2.0.x installation. /p p The Cocoon team has developed many Avalon components that are not specific to Cocoon @@ -131,8 +132,8 @@ pIn order to reflect the new version, the version information in the emcocoon.xconf/em has changed from em2.0/em to em2.1/em. /p -pWe suggest for updating the emcocoon.xconf/em to start with the new cocoon.xconf and - incorporate your changes instead of trying to migrate the old configuration file./p +pTo update emcocoon.xconf/em, 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./p /s2 s2 title=Source Resolver pThe SourceResolver is now an Avalon component @@ -204,11 +205,10 @@ pThe Store and StoreJanitor components and implementations have been moved to Avalon Excalibur./p pTo make upgrading easier, the class attributes of the store janitor - component has been removed in the emcocoon.xconf/em as the class names have changed. + component have been removed in emcocoon.xconf/em as the class names have changed. The emcache-transient/em and emcache-persistent/em components do - not exists anymore, so remove any reference from the cocoon.xconf. Instead - the empersistent-store/em and emtransient-store/em components - fulfil their tasks. + not exist anymore, so any reference to them must be removed from cocoon.xconf. + Use the empersistent-store/em and emtransient-store/em components instead. /p pIn general the package names changed from emorg.apache.cocoon.components.store/em to emorg.apache.excalibur.store/em (and emorg.apache.excalibur.store.impl/em). So
cvs commit: cocoon-2.1/src/documentation/xdocs/installing updating.xml
crossley2003/06/20 22:21:17 Modified:src/documentation/xdocs/installing updating.xml Log: Mention move of catalogs and entities to WEB-INF. Revision ChangesPath 1.9 +3 -0 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.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- updating.xml 18 Jun 2003 12:10:28 - 1.8 +++ updating.xml 21 Jun 2003 05:21:17 - 1.9 @@ -132,6 +132,9 @@ emorg.apache.cocoon.components.resolver.Resolver.ROLE/em anymore; use emorg.apache.excalibur.xml.EntityResolver.ROLE/em instead. /p +pThe default entities (DTDs, entity sets, etc.) have moved to the + WEB-INF/ directory. +/p /s2 s2 title=Stores pThe Store and StoreJanitor components and implementations have been moved to
cvs commit: cocoon-2.1/src/documentation/xdocs/installing updating.xml
bdelacretaz2003/06/18 05:01:17 Modified:src/documentation/xdocs/installing updating.xml Log: proofreading and general cleanup Revision ChangesPath 1.7 +106 -94 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.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- updating.xml 17 Jun 2003 13:41:26 - 1.6 +++ updating.xml 18 Jun 2003 12:01:17 - 1.7 @@ -7,173 +7,186 @@ authors person name=Carsten Ziegeler email=[EMAIL PROTECTED]/ person name=J#246;rg Heinicke email=[EMAIL PROTECTED]/ + person name=Bertrand Delacr#233;taz email=[EMAIL PROTECTED]/ /authors /header body s1 title=Updating Cocoon - pPlease take your time and read this document completly before you try to upgrade from + pPlease take your time to read this document completely before trying to upgrade from a Cocoon 2.0.x version to 2.1 (or above)./p p This is a brief discussion of the changes between the latest official release @released.version@ - and the current development version of Apache Cocoon. So, if you are interested in - installing the official release, ignore this document. But if you want to know what is going - on in the development of Cocoon, have a look... + 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. /p p - Cocoon has developed many Avalon components which are of a more general nature. So, the best - solution was to donate these components to the Avalon Excalibur project and move them out - of Cocoon. This move has lead to some changes in configuration etc. which are described - by this document. + The Cocoon team has developed many Avalon components which are not specific to Cocoon and have + been donated to the Avalon Excalibur project and moved out + of Cocoon. This has led to some configuration changes which are described + in this document. /p - pIn addition there were some disadvantages in the internal architecture of Cocoon. The -new version removes these bottlenecks and gives more flexibility, usability and performance. + p +The internal architecture of cocoon has also been improved to give more flexibility, usability and performance. /p /s1 s1 title=Sitemap - pThere are some changes in the sitemap and the configuration of some components in + pThere are some changes in the sitemap and in the configuration of some components in the sitemap./p s2 title=FOP Serializer -pFOP serializer's lt;user-configgt; relative path now resolves relative - to sitemap's directory. All Cocoon URIs are supported too./p +pRelative paths in FOP serializer's lt;user-configgt; are now resolved relatively + to the directory that contains the sitemap./p +pAll Cocoon URIs are supported too./p /s2 s2 title=Namespace changes -pIn order to follow strict rules for the namespace handling, some transformers - and generators changed their namespace, so if you use any of these components - make sure to change the namespaces./p +p +In order have more 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. +/p s3 title=Request Generator -pRequestGenerator changed namespace from http://xml.apache.org/cocoon/requestgenerator/2.0 to - http://apache.org/cocoon/request/2.0. +pRequestGenerator changed its namespace from http://xml.apache.org/cocoon/requestgenerator/2.0 to + http://apache.org/cocoon/request/2.0. /p /s3 s3 title=I18nTransformer - pThe I18nTransformer changed its namespace from - http://apache.org/cocoon/i18n/2.0 to http://apache.org/cocoon/i18n/2.1/p -/s3 -s3 title=I18nTransformer - pThe I18nTransformer changed its namespace from + pThe I18nTransformer changed its namespace from http://apache.org/cocoon/i18n/2.0 to http://apache.org/cocoon/i18n/2.1/p /s3 /s2 /s1 - s1 title=Recompiling Own Code -pDue to some changes in the logging of Cocoon components, for example own generators, - transformers or actions, code compiled for Cocoon 2.0.x will not run using - Cocoon 2.1./p -pIn order to get your own components running, you only have to recompile your code - and then everything should work fine./p + s1 title=Changes
cvs commit: cocoon-2.1/src/documentation/xdocs/installing updating.xml
cziegeler2003/06/18 05:10:29 Modified:src/documentation/xdocs/installing updating.xml Log: Minor typos Revision ChangesPath 1.8 +4 -3 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.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- updating.xml 18 Jun 2003 12:01:17 - 1.7 +++ updating.xml 18 Jun 2003 12:10:28 - 1.8 @@ -42,7 +42,7 @@ /s2 s2 title=Namespace changes p -In order have more consistent namespaces, some transformers +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. /p @@ -71,8 +71,9 @@ one change which shouldn't affect anybody (see below). /p s2 title=Source Resolver -pThe SourceResolver is an now Avalon component - which can be accessed using emcocoon.manager.lookup(SourceResolver.ROLE)./em/p +pThe SourceResolver is now an Avalon component + which can be accessed using emcocoon.manager.lookup(SourceResolver.ROLE)./em. + The package name of the component is emorg.apache.excalibur.source/em./p /s2 s2 title=XSLT Processor p
