Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 25374 invoked by uid 500); 5 Sep 2002 15:02:18 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 25355 invoked from network); 5 Sep 2002 15:02:18 -0000 Message-ID: <005301c254ec$c80ebfa0$0100a8c0@lux> From: "Jan Bromberger" To: References: Subject: Re: No SesionManager provided for Seleector? Date: Thu, 5 Sep 2002 16:59:05 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > When is your session context created? It should normaly be created only once on the first page request. At the moment for test purposes there is the following pipe: ... So it is created by the session transformer before the select state. I have now commented out the session create statement.. But nothing changes. Cheers, Jan Und danke fuers helfen! > > -----Original Message----- > > From: Jan Bromberger [mailto:vincev@gmx.de] > > Sent: Thursday, September 05, 2002 4:30 PM > > To: cocoon-users@xml.apache.org > > Subject: Re: No SesionManager provided for Seleector? > > > > > > > Ok, I'm not sure, but I think you can't lookup the SessionManager > > > in your compose() method. Try it in your select() method of > > > the Selector Interface. > > > That should work (I hope). > > > > Yes, thanks. That helps. > > But: The session that is provided is not the same as the one that I get > > with: > > > > ObjectModelHelper.getRequest(objectModel).getSession() > > > > Where objectModel is from > > > > public boolean select(final String expression, final Map objectModel, > > final Parameters parameters) { > > > > In the latter there is my SessionContext in the one provided by the > > SessionManager it is not. > > Do you have a clue why? > > > > > > > This should work, you can get a SessionManager from the > > > > > ComponentManager. > > > > > > > > > > What/how do you exactly try? > > > > > > > > public void compose(final ComponentManager componentManager) throws > > > > ComponentException { > > > > this.componentManager = componentManager; > > > > this.sessionManager = (SessionManager) > > > > componentManager.lookup(SessionManager.ROLE); > > > > } > > > > > > > > The stacktrace says: > > > > org.apache.avalon.framework.component.ComponentException: > > Could not find > > > > component > > > > at > > > > org.apache.avalon.excalibur.component.ExcaliburComponentManager.lo > > > > okup(Excal > > > > iburComponentManager.java:367) > > > > at > > > > org.apache.cocoon.components.CocoonComponentManager.lookup(CocoonC > > > > omponentMa > > > > nager.java:227) > > > > at > > > > org.apache.avalon.excalibur.component.DefaultComponentFactory$Comp > > > > onentManag > > > > erProxy.lookup DefaultComponentFactory.java:314) > > > > ... > > > > > > > > Cheers, > > > > Jan > > > > > > > > > -----Original Message----- > > > > > From: Jan Bromberger [mailto:vincev@gmx.de] > > > > > Sent: Thursday, September 05, 2002 3:47 PM > > > > > To: cocoon-users@xml.apache.org > > > > > Subject: No SesionManager provided for Seleector? > > > > > > > > > > > > > > > I intend to write a SessionContextSelector and tried to use a > > > > SessionManager > > > > > just like the SessionTransformer does. But it seems that there is no > > > > > SessionManager provided to a Selector while a Transformer gets one. > > > > > Am I right? > > > > > Why is that so? > > > > > And: Has anybody a suggestion for a workaround? > > > > > > > > > > Cheers, > > > > > Jan > > > > > > > > --------------------------------------------------------------------- > > Please check that your question has not already been answered in the > > FAQ before posting. > > > > To unsubscribe, e-mail: > > For additional commands, e-mail: > > > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. > > To unsubscribe, e-mail: > For additional commands, e-mail: > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: