Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 64672 invoked by uid 500); 14 Jan 2003 15:13:18 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 64661 invoked from network); 14 Jan 2003 15:13:18 -0000 Message-ID: <3E24291A.1000203@apache.org> Date: Tue, 14 Jan 2003 15:13:30 +0000 From: Stefano Mazzocchi User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: Flow-questions References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Carsten Ziegeler wrote: > Ugo Cei wrote: > >>Mats Nor�n wrote: >> >>>Hi, >>>I�ve been looking at the code for the flow layer and I have a couple of >>>questions: >>> >>>Is there any way for me to get access to the component-manager within >>>the flow layer? >> >>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. ?? then why is it part of the Environment? > Isn't it possible to use the usual Composable stuff? what do you mean? -- Stefano Mazzocchi -------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org