cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Unico Hommes" <Un...@hippo.nl>
Subject RE: processPipelineTo[Stream|SAX|DOM]
Date Thu, 11 Dec 2003 21:54:53 GMT

Sylvain Wallez wrote:
> 
> One more new feature ;-)
> 
> Following the thread "extending FOM" about extending 
> processPipelineTo 
> to SAX and DOM, I wrote a utility class that handles all this.
> 
> This class is totally decorrelated from the FOM and the 
> "cocoon" object 
> and provides the processToDOM(), processToSAX() and processToStream() 
> methods. Here's a usage example to get a DOM:
> 
>   var pipelineUtil = 
> cocoon.createObject(Packages.org.apache.cocoon.components.flow
> .util.PipelineUtil);
>   var doc = pipelineUtil.processToDOM("my-pipeline", { foo:bar });
>   // do something with "doc", such as binding to a woody form
> 
> This class replaces and extends "cocoon.processPipelineTo". Being 
> implemented totally externally to the flow engine, it shows that this 
> method isn't actually core to the FOM.
> 

Damn dude, you just keep 'em coming ;-) Excellent! This is going to be
soooo useful. Now, DOM is really official and flashy and all but, can I
add a processToConfiguration too?

> So what about deprecating "cocoon.processPipelineTo" from the 
> official 
> FOM and direct users to the new class ?
> 

Hmm, don't realy have an opinion on this. I guess.

Cheers, Unico

Mime
View raw message