cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew C. Oliver" <acoli...@apache.org>
Subject Re: [RT] Making Cocoon instance available to other components
Date Fri, 29 Nov 2002 17:27:13 GMT
Right.  I've seen it.  He said it doesnn't "need" to be.  Thats the part 
I disagreed with.

Nicola Ken Barozzi wrote:

>
> Andrew C. Oliver wrote:
>
>> I disagree.  It should be a component.  What if I want to use cocoon 
>> for transformations/etc outside the context of a servlet?  (I might 
>> soon).
>
>
> A container can be - usually is - also a component.
>
> Look for example at Tweety on Avalon, it's a container, but also a 
> component.
>
>> -Andy
>>
>>>
>>> The Cocoon object is an Avalon component, but in fact doesn't need 
>>> to be : it is conceptually a container, which loads the 
>>> configuration, creates an ECM and delegates the implementation of 
>>> the Processor interface to the component implementing this interface 
>>> that is managed by the ECM (look at Cocoon.process()).
>>>
>>> So what you are looking for may be simply looking up the Processor 
>>> role in the ECM that manages your component, which will return the 
>>> sitemap engine, and call process() on that object.
>>>
>>> Hope this helps,
>>> Sylvain
>>>
>
>




---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message