Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Carsten Ziegeler" <cziegeler@s-und-n.de>
To: <cocoon-dev@xml.apache.org>
Subject: RE: Why does moving the portal-fw from samples break it?
 (PortalManager not found on 'save')
Date: Wed, 18 Jun 2003 14:16:40 +0200
Message-ID: <LKENJPKDAIKAPKHEOCMMIEKCDPAA.cziegeler@s-und-n.de>
MIME-Version: 1.0
In-Reply-To: <20030617181034.GE61099@juniper.net>
Importance: Normal
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="us-ascii"


> -----Original Message-----
> From: Rob Johnston [mailto:rjohnst@juniper.net]
> Sent: Tuesday, June 17, 2003 8:11 PM
> To: cocoon-dev@xml.apache.org
> Subject: Why does moving the portal-fw from samples break it?
> (PortalManager not found on 'save')
> 
> 
> 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.
> 
This exception is not the real cause, I guess. When save is hit, the
saving is done "during" the lookup of the portal manager - so if
something goes wrong during saving, the above exception will result.
Can you provide the real cause (it should be somewhere hidden in the
large stack-trace)?

Carsten