cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wolfram Eisert <eis...@philasearch.com>
Subject Re: Porting to current cocoon version
Date Mon, 16 Jan 2012 13:54:25 GMT
Hello Jos,

does that mean there is no xsp available in Cocoon 3 at all or that it's
just not recommended?

Wolfram

2012/1/16 Jos Snellings <Jos.Snellings@pandora.be>

> **
> Dear mr. Eisert,
>
> 1.  I believe it does. I am using the beta version in a "preproduction
> environment" for quite some time and it is stable.
> 2. It depends on what you mean by configuration. The sitemap will need
> some slight adaptations.
>     Specifics from cocoon 2.2 will no longer hold.
>     - no flowscripts
>     - xsp is "banned"
>     There is a nonvanishing upgrade effort.
> 3. no, it should be written. I never used all of cocoon 2.x, but from my
> experience:
>     - start project from 'cocoon sample and cocoon sample webapp'
>     - plan need for conversion scripts
>     - adapt sitemap
>     - adjust configuration (which is now essentially spring configuration)
>
> it depends a great deal on what you have been using in cocoon 2.x.
>
> Jos
>
>
> On 01/16/2012 12:51 PM, Wolfram Eisert wrote:
>
> Dear List,
>
>  we are currently using Cocoon 2.0.4 and plan to update to a newer
> version during this year.
>
>  For that I have a few questions:
>
>    - Does it make sense to wait for Cocoon 3.0?
>    - Is the configuration compatible between Cocoon 2.2 and Cocoon 3.0?
>    - Is there a "howto" for moving from Cocoon 2.0.4 to a current Version?
>
>  Thank you for your answers.
>
>  Wolfram
>
>
>


-- 
*
*
Philasearch.com GmbH
Lindenweg 1
D-63877 Sailauf
Tel. 06093-932933

Geschäftsführer: Franz Fedra, Wolfram Eisert, Walter Christ
Steuer-Nr.:204 135 10911 Finanzamt Aschaffenburg
Umsatzsteuer-
Identifikationsnummer
gemäß § 27 a Umsatzsteuergesetz: DE 112156180

Mime
View raw message