RE: What is supported in Cocoon 1.x and no longer supported in 2. 0

["Williams, Murray Todd" <mu...@merck.com>]

> ----------
> From: 	Gambale, Michael J.[SMTP:michael_gambale@merck.com]
> Reply To: 	cocoon-users@xml.apache.org
> Sent: 	Monday, May 01, 2000 10:21 AM
> To: 	'cocoon-users@xml.apache.org'
> Subject: 	What is supported in Cocoon 1.x and no longer supported in
> 2.0
> 
> I wanted to ask this question because my group is seriously considering
> writing an XML based web site using Cocoon.
> 
> We are using the XML and XSL transformation(this is what I'm not worried
> about) as well as XSP.  We're using XSP to also dynamically build the DOM
> tree.  Are there any issues with Cocoon 2.0 and its use of using the SAX
> parser versus DOM as to affect what we are doing?  I may be confused so
> set
> me straight.  I just want to make sure we can upgrade without any
> problems.
> Basically I guess the question is what can't we do in Cocoon 1.x that
> won't
> be supported in Cocoon 2.0.
> 
> 
> Thanks.
> 
> -Mike
> 
I was just about to ask a very similar question of the mailing list. I'm
wanting to write a custom Processor (and maybe also a Producer) for Cocoon,
but I don't want to do a full and complete rewrite for Cocoon2.

Re: What is supported in Cocoon 1.x and no longer supported in 2. 0

[Ross Burton <ro...@mail.com>]

> I was just about to ask a very similar question of the mailing list. I'm
> wanting to write a custom Processor (and maybe also a Producer) for
Cocoon,
> but I don't want to do a full and complete rewrite for Cocoon2.

Cocoon 2 is fully SAX2-based - no DOM is used directly by the core engine.
However, the are several classes (org.apache.cocooon.xml.util.DOMBuilder et
al) which handle the reading of SAX2 events and create a DOM Document
object.  As long as your producers/processors are modular, porting to Cocoon
2 should be fairly simple.

Ross Burton

Re: What is supported in Cocoon 1.x and no longer supported in 2. 0

[Giacomo Pati <Gi...@pwr.ch>]

"Williams, Murray Todd" wrote:
> 
> (Input) DOM Document --> SAX Events --> SAX "Filter" --> SAX Events -->
> (Output) DOM Document
> 

There are some utility classes in the cocoon 2 cvs (DOMStreamer.java,
DOMBuilder.java) which can be used to stream a DOM to a DocumentHandler
or to build a DOM out of SAX Events. May be you can use these.

> 
> I suspect that writing XSP material to built DOM structures is going to
> cause major portability problems to Cocoon2.
> 

I think "standard" XSP will not cause major problems using them later in
cocoon 2. If you have written taglibs these of course can be a problem
and will have to be converted.

Giacomo

-- 
PWR Organisation & Entwicklung            Tel:   +41 (0)1 856 2202
Giacomo Pati, CTO/CEO                     Fax:   +41 (0)1 856 2201
Hintereichenstrasse 7                     Mailto:Giacomo.Pati@pwr.ch
CH-8166 Niederweningen                    Web:   http://www.pwr.ch

Re: What is supported in Cocoon 1.x and no longer supported in 2. 0

[Paul Russell <pa...@luminas.co.uk>]

On Mon, May 01, 2000 at 10:48:07AM -0400, Williams, Murray Todd wrote:
> [...] I imagine the way to go is to write a Cocoon1
> Processor with the basic structure
> 
> (Input) DOM Document --> SAX Events --> SAX "Filter" --> SAX Events -->
> (Output) DOM Document

Cocoon2 already has two classes (org.apache.cocoon.xml.util.DOMBuilder and
org.apache.cocoon.xml.util.DOMStreamer) for doing this. If the peeps with
CVS commit status agree with the methodology, they might add those files to
the active (cocoon1) branch.

-- 
Paul Russell                               <pa...@luminas.co.uk>
Technical Director,                   http://www.luminas.co.uk
Luminas Ltd.