cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Johnston <rjoh...@juniper.net>
Subject Why does moving the portal-fw from samples break it? (PortalManager not found on 'save')
Date Tue, 17 Jun 2003 18:10:34 GMT
I've attempted to move the portal-fw sample from the samples dir into
the main sitemap (I copied everything that needed to be copied -- the
component-configurations block, all the pipelines, etc verbatim).
I also moved all the files from samples/portal-fw/* into the main webapp dir.

Everything works fine (changing roles, moving things around, etc) until you
attempt to save the logged in userprofile.  (Customize -> Save).  You then get
this error:

Internal Server Error

Message: Lookup of PortalManager failed.

Description: org.apache.cocoon.ProcessingException: Lookup of PortalManager failed.: org.apache.avalon.framework.component.ComponentException:
Could not find component (key [org.apache.cocoon.webapps.portal.components.PortalManager])

Sender: org.apache.cocoon.servlet.CocoonServlet

Source: Cocoon Servlet

request-uri

/sunspotdemo-portlets

full exception chain stacktrace

Original Exception: org.apache.avalon.framework.component.ComponentException: Could not find
component (key [org.apache.cocoon.webapps.portal.components.PortalManager])
	at org.apache.avalon.excalibur.component.ExcaliburComponentManager.lookup(ExcaliburComponentManager.java:295)
	at org.apache.cocoon.components.CocoonComponentManager.lookup(CocoonComponentManager.java:288)
	at org.apache.avalon.excalibur.component.DefaultComponentFactory$ComponentManagerProxy.lookup(DefaultComponentFactory.java:437)
	at org.apache.avalon.excalibur.component.DefaultComponentFactory$ComponentManagerProxy.lookup(DefaultComponentFactory.java:437)
	at org.apache.cocoon.webapps.portal.generation.PortalGenerator.generate(PortalGenerator.java:83)
	at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.processXMLPipeline(AbstractProcessingPipeline.java:545)
	at org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.processXMLPipeline(AbstractCachingProcessingPipeline.java:218)
	at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:489)
	at org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(SerializeNode.java:150)
	at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:84)
	at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:164)

... etc

Why would moving the physical location of this sample cause this?  Was
there some change to the cocoon:raw:/ protocol that wasn't changed in
the portal-fw example and this is what is breaking it?

thanks,
rob

----- End forwarded message -----

Mime
View raw message