cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ovidiu Predescu <ovi...@apache.org>
Subject Re: Flow-questions
Date Tue, 14 Jan 2003 18:05:13 GMT

On Tuesday, Jan 14, 2003, at 06:18 US/Pacific, Ugo Cei wrote:

> Carsten Ziegeler wrote:
>>> cocoon.environment.getComponentManager() should do the trick. Haven't
>>> tested it though.
>> I warn you using the method above, because it's an internally used 
>> method
>> which should not be access from own components.
>> Isn't it possible to use the usual Composable stuff?
>
> A brief look at the API docs for the JSCocoon class reveals that you 
> should be able to access the manager as a property of the "cocoon" 
> object, as in:
>
> 	var manager = cocoon.componentManager;
>
> Even though JSCocoon does not implement Composable, somehow a manger 
> is passed to it via the setContext() method, so I suppose it is set by 
> the Composable that creates JSCocoon, whatever it is.

Yes, this is exactly right, you can use the componentManager accessible 
through the 'cocoon' global variable.

> I'll let Ovidiu comment on this, as soon as he's finished unpacking 
> his bags ;-).

I've done it before, hope you don't mind :)

Cheers,
-- 
Ovidiu Predescu <ovidiu@apache.org>
http://www.google.com/search?btnI=&q=ovidiu (Are you feeling lucky?)


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


Mime
View raw message