Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 56048 invoked by uid 500); 7 Sep 2002 12:23:32 -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 56037 invoked from network); 7 Sep 2002 12:23:32 -0000 Message-ID: <3D79EF8B.1020402@verizon.net> Date: Sat, 07 Sep 2002 08:22:35 -0400 From: Vadim Gritsenko User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: SourceFactory lifecycles References: <5.1.0.14.0.20020907203611.01af7c00@192.168.0.5> <5.1.0.14.0.20020907211605.02d8a838@192.168.0.5> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Robert Leftwich wrote: > At 09:00 PM 7/09/2002, Stephen McConnell wrote: > >> A couple of questions: >> >> 1. which container are you using? > > > If you mean servlet container, it's Resin 2.1.4 (on W2000) using the > snapshot xml-cocoon2_20020905222323 with patch 12115 applied (for a > NPE in AbstractCachingProcessingPipeline.java) > >> 2. is it really the case that the same instance is being configured >> twice (or is it two instance with one configuration invocation for >> each instance) > > > I was checking this even as you wrote :-) It's actually a new instance > per request with each being configured once. Are you implementing ThreadSafe, as FileSourceFactory.java does? Vadim > Robert --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org