cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leo Sutic" <leo.su...@inspireinfrastructure.com>
Subject RE: CocoonComponentManager
Date Fri, 16 Apr 2004 10:42:24 GMT


> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de] 
>
> This would give everyone access to the info (ok, the current 
> static methods are accessible as well) and imho makes it more 
> visible.

I think it'd make it less visible. For example, you can pass the
CocoonContext only to specific components, while the statics
are available everywhere.

> Just curious, why do want to do this? Do you just want to use 
> the TreeProcessor as a processor for a custom XML? Or are you 
> using the TreeProcessor to process a sitemap in a different 
> environment? Now, I think, if the TreeProcessor is used for 
> custom XML, then you could use the TreeBuilder I think (I'm 
> not that sure). If you want to process a sitemap, you need 
> the dependency to the cocoon stuff anyway.

I will process a reduced sitemap. Just generators, actions,
transformers and serializers. Nothing more. In theory I
could define my own pipeline language, write my own components,
and so on, but I figured I'd try to re-use as much of Cocoon
as possible. 

Specifically, I will not be using flow, continuations or 
subsitemaps.

/LS


Mime
View raw message