From dev-return-103330-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Mon Jan 16 14:37:06 2012 Return-Path: X-Original-To: apmail-cocoon-dev-archive@www.apache.org Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E1C49B76C for ; Mon, 16 Jan 2012 14:37:06 +0000 (UTC) Received: (qmail 32431 invoked by uid 500); 16 Jan 2012 14:37:06 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 32313 invoked by uid 500); 16 Jan 2012 14:37:05 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 32306 invoked by uid 99); 16 Jan 2012 14:37:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Jan 2012 14:37:05 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [57.67.164.70] (HELO be1ssnxpe2.nxp.com) (57.67.164.70) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Jan 2012 14:36:59 +0000 Received: from EU1RDCRDC1VW025.exi.nxp.com ([134.27.176.170]) by be1ssnxpe2.nxp.com (8.14.4/8.14.4) with ESMTP id q0GEaa4O000610 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Mon, 16 Jan 2012 15:36:36 +0100 Received: from eu1rdcrdc1wx032.exi.nxp.com ([134.27.179.186]) by EU1RDCRDC1VW025.exi.nxp.com ([134.27.176.170]) with mapi; Mon, 16 Jan 2012 15:36:36 +0100 From: Robby Pelssers To: "dev@cocoon.apache.org" Date: Mon, 16 Jan 2012 15:36:34 +0100 Subject: RE: Porting to current cocoon version Thread-Topic: Porting to current cocoon version Thread-Index: AczUV+e4Rn4ea9X5TQ+cwIfMfzgLGAAA7suA Message-ID: <78B923726E7D59429936580CF127E943A1F58D19F4@eu1rdcrdc1wx032.exi.nxp.com> References: <4F14275A.6010104@pandora.be> <4F142E7A.6020701@pandora.be> In-Reply-To: <4F142E7A.6020701@pandora.be> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_78B923726E7D59429936580CF127E943A1F58D19F4eu1rdcrdc1wx0_" MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.5.7110,1.0.211,0.0.0000 definitions=2012-01-16_01:2012-01-16,2012-01-16,1970-01-01 signatures=0 --_000_78B923726E7D59429936580CF127E943A1F58D19F4eu1rdcrdc1wx0_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I totally agree with Jos. If your app mainly consists of transformations w= ith XSLT, you should be able to migrate within a few days. If your complet= e app depends on XSP's you will have to spent a lot more time of course. Bu= t we've been in the same situation and I guess 2 or 3 people should be able= to manage to port in a matter of 1 a 2 weeks. I advise you to first follo= w the samples demo and try to implement a few small use cases from your exi= sting app. If you run into any issue address this to the mailinglist in or= der to evaluate the risks upfront. Robby From: Jos Snellings [mailto:Jos.Snellings@pandora.be] Sent: Monday, January 16, 2012 3:05 PM To: dev@cocoon.apache.org Subject: Re: Porting to current cocoon version Hello Wolfram, The first. Cocoon 3 is rather a complete rewrite of the framework. The benefit: the dependencies of the framework have been limited to a minim= um. A half-advantage: the scripting capabilities have been limited to stringtem= plate. This sort of enforces scripts to do 'strictly presentation'. The minus side: old xsp scripts have to be rewritten. It all depends on how many xsp and flow scripts you have out there. Kind regards, Jos On 01/16/2012 02:54 PM, Wolfram Eisert wrote: Hello Jos, does that mean there is no xsp available in Cocoon 3 at all or that it's ju= st not recommended? Wolfram 2012/1/16 Jos Snellings > Dear mr. Eisert, 1. I believe it does. I am using the beta version in a "preproduction envi= ronment" 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 ex= perience: - 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 d= uring 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=E4ftsf=FChrer: Franz Fedra, Wolfram Eisert, Walter Christ Steuer-Nr.:204 135 10911 Finanzamt Aschaffenburg Umsatzsteuer- Identifikationsnummer gem=E4=DF =A7 27 a Umsatzsteuergesetz: DE 112156180 --_000_78B923726E7D59429936580CF127E943A1F58D19F4eu1rdcrdc1wx0_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

= I totally agree with Jos.=A0 If your app mainly consists of transfor= mations with XSLT, you should be able to migrate within a few days.=A0 If y= our complete app depends on XSP’s you will have to spent a lot more t= ime of course. But we’ve been in the same situation and I guess 2 or = 3 people should be able to manage to port in a matter of 1 a 2 weeks.=A0 I = advise you to first follow the samples demo and try to implement a few smal= l use cases from your existing app.=A0 If you run into any issue address th= is to the mailinglist in order to evaluate the risks upfront.

<= /o:p>

Robby

 

From: Jos Snellings [mailto:Jo= s.Snellings@pandora.be]
Sent: Monday, January 16, 2012 3:05 PMTo: dev@cocoon.apache.org
Subject: Re: Porting to curren= t cocoon version

 

Hello Wolfram,

The first. Coco= on 3 is rather a complete rewrite of the framework.
The benefit: the dep= endencies of the framework have been limited to a minimum.
A half-advant= age: the scripting capabilities have been limited to stringtemplate. This s= ort of enforces scripts to do 'strictly presentation'.
The minus side:&n= bsp; old xsp scripts have to be rewritten.
It all depends on how many xs= p and flow scripts you have out there.

Kind regards,
Jos

O= n 01/16/2012 02:54 PM, Wolfram Eisert wrote:

Hello Jos,

 =

does that mean there is no xsp availabl= e 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 site= map 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 u= sed all of cocoon 2.x, but from my experience:
    - star= t project from 'cocoon sample and cocoon sample webapp'
  &nbs= p; - plan need for conversion scripts
    - adapt sitemap=
    - adjust configuration (which is now essentially spr= ing configuration)
   
it depends a great deal on wha= t you have been using in cocoon 2.x.

<= span class=3Dhoenzb>Jos



On 01/16/2012 12:51 PM, Wolfram Eisert wrote: <= /p>

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 s= ense to wait for Cocoon 3.0?
  • Is the configuration compatible between Cocoon 2.2 and Cocoon 3.0?
  • Is there a "howto" for mo= ving from Cocoon 2.0.4 to a current Version?

Thank you for your answers.

=

 

W= olfram

 

=



<= div>

 

--

Philasearch.com GmbH

Lindenweg 1
D-63= 877 Sailauf
Tel. 06093-932933

Gesch=E4ftsf=FChrer: Franz Fedra, W= olfram Eisert, Walter Christ
Steuer-Nr.:204 135 10911 Finanzamt Aschaffe= nburg
Umsatzsteuer-

Identifikationsnummer
gem=E4=DF =A7 27 a Ums= atzsteuergesetz: DE 112156180

 

 

= --_000_78B923726E7D59429936580CF127E943A1F58D19F4eu1rdcrdc1wx0_--