Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-Id: <5.1.0.14.0.20020908063644.01b14b18@192.168.0.5>
Date: Sun, 08 Sep 2002 06:46:49 +1000
To: cocoon-dev@xml.apache.org
From: Robert Leftwich <robert@leftwich.info>
Subject: Re: SourceFactory lifecycles
In-Reply-To: <3D7A3BD4.8030002@apache.org>
References: <5.1.0.14.0.20020907203611.01af7c00@192.168.0.5>
 <5.1.0.14.0.20020907211605.02d8a838@192.168.0.5>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 03:48 AM 8/09/2002, Stephen McConnell wrote:

>What I actually mean was - which "component container" are you using and 
>the answer is the ECM (Excalibur Componnet Manager varient on which Cocoon 
>is based).

Excuse my newbie misunderstanding :-)

>Which means that the lifestyle declaration is the issue you need to deal 
>with (thread-safe, per-thread, etc.).

Yep, what threw me was that there is no mention of thread-based lifecycle 
interactions in the Avalon page on the component lifecycles, so I made a 
(bad) assumption.

>My guess is that you have a configuration which is declaring a lifestyle 
>policy of a new instance per request and you actually want something like 
>per-thread of a singleton policy.

Spot on - ThreadSafe appears to do it for me, is that the correct 
declaration for singleton behavior?

Robert


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org