Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 62601 invoked by uid 500); 30 May 2002 08:16:36 -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 62590 invoked from network); 30 May 2002 08:16:36 -0000 Date: Thu, 30 May 2002 10:15:12 +0200 (CEST) From: Stephan Michels To: cocoon-dev Subject: RE: [ROLES]Something changed? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Wed, 29 May 2002, Carsten Ziegeler wrote: > > -----Original Message----- > > From: Stephan Michels [mailto:stephan@vern.chem.tu-berlin.de] > > On Wed, 29 May 2002, Carsten Ziegeler wrote: > > > > > The latest CVS works for me. Hmm, do you have a handlers configuration > > > in the auth-protect action? The authentication manager is currently > > > very picky if this is missing. > > > > > > > I have following entries in my sitemap: > > > > > src="org.apache.cocoon.webapps.authentication.acting.AuthAction"> > > > > > xmlns:map="http://apache.org/cocoon/sitemap/1.0"> > > > > > > > > > > > > > Ok, looks good to me - if you happen to use the latest CVS from today, > you have to move this configuration from the action to the map:pipelines > section. You can have a look at an example if you build the webapp. > > Do you have a configuration for the authentication-manager in the > cocoon.xconf. The default entry created by build webapp is required > currently! With the current CVS snapshot from today I get a different exception: DEBUG (2002-05-30) 10:04.59:997 [sitemap](/login.html) HttpProcessor[8080][4]/InvokeContext: Current Sitemap Parameters: PARAM: '0' VALUE: 'login.html' WARN (2002-05-30) 10:04.59:998 [sitemap](/login.html) HttpProcessor[8080][4]/PipelineNode: Error while processing pipeline at jndi:/localhost/sitemap.xmap:290:17 org.apache.avalon.framework.component.ComponentException: UnnamedSelector: ComponentSelector Attempted to retrieve component with null hint. at org.apache.avalon.excalibur.component.ExcaliburComponentSelector.select(ExcaliburComponentSelector.java:245) at org.apache.cocoon.sitemap.DefaultSitemapComponentSelector.select(DefaultSitemapComponentSelector.java:109) at org.apache.cocoon.components.treeprocessor.InvokeContext.getProcessingPipeline(InvokeContext.java:169) at org.apache.cocoon.components.treeprocessor.sitemap.ReadNode.invoke(ReadNode.java:106) [...] WARN (2002-05-30) 10:05.00:115 [sitemap](/login.html) HttpProcessor[8080][4]/ExcaliburComponentManager: ComponentManager exception from parent CM during lookup. org.apache.avalon.framework.component.ComponentException: Could not find component at org.apache.avalon.excalibur.component.ExcaliburComponentManager.lookup(ExcaliburComponentManager.java:340) at org.apache.cocoon.components.CocoonComponentManager.lookup(CocoonComponentManager.java:215) at org.apache.avalon.excalibur.component.DefaultComponentFactory$ComponentManagerProxy.lookup(DefaultComponentFactory.java:319) at org.apache.avalon.excalibur.component.ExcaliburComponentManager.lookup(ExcaliburComponentManager.java:273) at org.apache.cocoon.components.CocoonComponentManager.lookup(CocoonComponentManager.java:215) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invokeErrorHandler(PipelineNode.java:208) [...] It seems, that ReadNode from the TreeProcessor can't look up for the reader. But in the sitemap I got following entries. [...] [...] [...] --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org