From dev-return-102737-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Wed Jun 8 10:09:14 2011 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 F409B48E6 for ; Wed, 8 Jun 2011 10:09:13 +0000 (UTC) Received: (qmail 88914 invoked by uid 500); 8 Jun 2011 10:09:13 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 88816 invoked by uid 500); 8 Jun 2011 10:09:12 -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 88809 invoked by uid 99); 8 Jun 2011 10:09:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jun 2011 10:09:12 +0000 X-ASF-Spam-Status: No, hits=2.9 required=5.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [78.134.5.44] (HELO rovere.tirasa.net) (78.134.5.44) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jun 2011 10:09:08 +0000 Received: from [192.168.0.2] (mogano.tirasa.net [192.168.0.2]) by rovere.tirasa.net (Postfix) with ESMTPSA id 6059817F5CA for ; Wed, 8 Jun 2011 12:07:13 +0200 (CEST) Message-ID: <4DEF4A2C.7050907@apache.org> Date: Wed, 08 Jun 2011 12:08:44 +0200 From: =?ISO-8859-15?Q?Francesco_Chicchiricc=F2?= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: [C3] Fwd: [Hippo-cms7-user] Cocoon 3 based frontend Content-Type: multipart/alternative; boundary="------------050005050809060909040405" This is a multi-part message in MIME format. --------------050005050809060909040405 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit Hi there, fist of all, sorry for the cross-posting. You can find below an e-mail that I've just sent to the Hippo CMS mailing list. There is some concrete possibility to use Cocoon 3 in a (rather small, as said) production environment. I would basically like to build a JCR SAX transformer (similar in functions to the Cocoon 2.1 WebDAV transformer) but I would also need, for example, some caching and i18n features. Do you see any particular issues besides the obvious risk of using an Alpha-2 (not yet Alpha-3) software for production? ;-) -------- Messaggio originale -------- Oggetto: [Hippo-cms7-user] Cocoon 3 based frontend Data: Wed, 08 Jun 2011 12:02:32 +0200 Mittente: Francesco Chicchiriccò Rispondi-a: Hippo CMS 7 development public mailinglist Organizzazione: Tirasa A: Hippo CMS 7 development public mailinglist Hi all, we've recently got a (rather small, indeed) customer with a very particular need: to be able, in the near future, to migrate either all the documents from its current legacy CMS and also all of its Cocoon 2.1 sites. They basically want to preserve - as much as possible - past investments done in terms of XSLTs and components. We are now defining the basic structure of our project and we do want to put Hippo CMS 7.6 in place. Of course this would mean to replace all the HST2 stuff that is normally involved when building sites with some Cocoon-based components. Looking at the documentation, I've found this reference to the Hippo's JCR interface [1]. Do you think it would be fine to build something that will interact with Hippo repository at that level or instead there are some higher-level classes from HST2 that should instead taken into account? Do you have any particular advice when doing such operation? Is there any more documentation we should take a look at? Thanks. [1] http://www.onehippo.org/cms7/documentation/development/content+repository/jcr/index.html -- Dott. Francesco Chicchiriccò Tel +393290573276 Amministratore unico @ Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 0859111173 http://www.tirasa.net Apache Cocoon Committer and PMC Member http://people.apache.org/~ilgrosso/ "To Iterate is Human, to Recurse, Divine" (James O. Coplien, Bell Labs) _______________________________________________ Hippo-cms7-user mailing list and forums http://www.onehippo.org/cms7/support/forums.html --------------050005050809060909040405 Content-Type: text/html; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Hi there,
fist of all, sorry for the cross-posting.

You can find below an e-mail that I've just sent to the Hippo CMS mailing list.
There is some concrete possibility to use Cocoon 3 in a (rather small, as said) production environment.

I would basically like to build a JCR SAX transformer (similar in functions to the Cocoon 2.1 WebDAV transformer) but I would also need, for example, some caching and i18n features.

Do you see any particular issues besides the obvious risk of using an Alpha-2 (not yet Alpha-3) software for production? ;-)

-------- Messaggio originale --------
Oggetto: [Hippo-cms7-user] Cocoon 3 based frontend
Data: Wed, 08 Jun 2011 12:02:32 +0200
Mittente: Francesco Chicchiriccò <francesco.chicchiricco@tirasa.net>
Rispondi-a: Hippo CMS 7 development public mailinglist <hippo-cms7-user@lists.onehippo.com>
Organizzazione: Tirasa
A: Hippo CMS 7 development public mailinglist <hippo-cms7-user@lists.onehippo.com>


Hi all,
we've recently got a (rather small, indeed) customer with a very 
particular need: to be able, in the near future, to migrate either all 
the documents from its current legacy CMS and also all of its Cocoon 2.1 
sites.
They basically want to preserve - as much as possible - past investments 
done in terms of XSLTs and components.

We are now defining the basic structure of our project and we do want to 
put Hippo CMS 7.6 in place. Of course this would mean to replace all the 
HST2 stuff that is normally involved when building sites with some 
Cocoon-based components.

Looking at the documentation, I've found this reference to the Hippo's 
JCR interface [1]. Do you think it would be fine to build something that 
will interact with Hippo repository at that level or instead there are 
some higher-level classes from HST2 that should instead taken into account?

Do you have any particular advice when doing such operation? Is there 
any more documentation we should take a look at?

Thanks.

[1] 
http://www.onehippo.org/cms7/documentation/development/content+repository/jcr/index.html

-- 
Dott. Francesco Chicchiriccò
Tel +393290573276

Amministratore unico @ Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 0859111173
http://www.tirasa.net

Apache Cocoon Committer and PMC Member
http://people.apache.org/~ilgrosso/

"To Iterate is Human, to Recurse, Divine"
(James O. Coplien, Bell Labs)

_______________________________________________
Hippo-cms7-user mailing list and forums
http://www.onehippo.org/cms7/support/forums.html
--------------050005050809060909040405--