Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Date: Mon, 01 May 2000 14:23:47 -0400
From: "Williams, Murray Todd" <murray_williams@merck.com>
Subject: RE: What is supported in Cocoon 1.x and no longer supported in 2.	0
To: "'cocoon-users@xml.apache.org'" <cocoon-users@xml.apache.org>
Message-id: <1161B9F1E3E5D111A25700A02461F2AB02B37FB1@usrymx04.merck.com>
MIME-version: 1.0
Content-type: text/plain
Content-transfer-encoding: 7BIT

Ross, is this org.apache.cocoon.xml.util.DOMBuilder only in Cocoon2?  I
can't find any such creature among the Cocoon1 apiDocs or source.  Do you
know of anything that goes the other way?  Ie: something that takes a DOM
Document and communicates with a ContentHandler?

Murray

> ----------
> From: 	Ross Burton[SMTP:ross.burton@mail.com]
> Reply To: 	cocoon-users@xml.apache.org
> Sent: 	Monday, May 01, 2000 12:53 PM
> To: 	cocoon-users@xml.apache.org
> Subject: 	Re: What is supported in Cocoon 1.x and no longer supported
> in 2.	0
> 
> > 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
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
>