Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <434E2052.5060200@apache.org>
Date: Thu, 13 Oct 2005 10:52:34 +0200
From: Carsten Ziegeler <cziegeler@apache.org>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Portal won't start in trunk
References: <434D5078.5010902@dslextreme.com>
 <434D52DD.9080703@reverycodes.com> <434D5497.2040403@apache.org>
 <434D5F98.3090101@reverycodes.com> <434D6878.2000403@apache.org>
 <434E1C67.5040706@apache.org>
In-Reply-To: <434E1C67.5040706@apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Sylvain Wallez wrote:
> 
> Fixed. The problem was caused by the GroupBasedProfileManager which was 
> not preloaded and thus wasn't listening for events. This led the portal 
> temporary attribute (don't know what that is) named 
> "org.apache.cocoon.portal.profile.impl.AbstractProfileManager/User" not 
> being initialized, thus the NPE.
> 
> The lazy loading brings some interesting performance improvements by 
> avoiding not only the initialization of components, but also even the 
> loading of classes. Problem is that it requires configuration writers to 
> know what components have to be loaded at startup time.
> 
> So maybe we should be a bit less lazy, and load the classes to check for 
> a lifecycle interface (Startable?) to avoid having to specify 
> preload="true" in the configuration. I'll check this and see the speed 
> difference.
> 
+1

Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/