Return-Path: Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 30865 invoked by uid 500); 20 Jun 2003 14:19:44 -0000 Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list dev@avalon.apache.org Received: (qmail 30786 invoked from network); 20 Jun 2003 14:19:43 -0000 Received: from nan-smtp-01.noos.net (HELO smtp.noos.fr) (212.198.2.70) by daedalus.apache.org with SMTP; 20 Jun 2003 14:19:43 -0000 Received: (qmail 23881046 invoked by uid 0); 20 Jun 2003 14:19:42 -0000 Received: from unknown (HELO apache.org) ([212.198.17.4]) (envelope-sender ) by 212.198.2.70 (qmail-ldap-1.03) with SMTP for ; 20 Jun 2003 14:19:42 -0000 Message-ID: <3EF3186F.1060307@apache.org> Date: Fri, 20 Jun 2003 16:21:35 +0200 From: Stephen McConnell User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.4) Gecko/20030529 X-Accept-Language: en, en-us MIME-Version: 1.0 To: Avalon Developers List Subject: Re: [merlin] singleton not really a singleton ?? References: <3EF30C79.3060508@jentro.com> In-Reply-To: <3EF30C79.3060508@jentro.com> 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 kristian meier wrote: > Hi, > > since I made a new build this week I have problems with components > which are marked as singletons in the xtype-file > but get instantiated serveral times. > > my setup is the following: > > > > > this configuration starts fine and works correct. but if I an add > attribute activation="startup" to the "http-server" component than at > time of instanciating the "find-proxy-ip" component I get an "address > already in use"-exception, because a second instance of the > "http-server" is created :-( That's not good! > > the old build I use the last 2-3 weeks worked fine. so the question is > moreless: is this a bug or a feature ? It's a bug. I was doing messing with the activation policy stuff a couple of weeks ago - looks like I've done something silly. > for me the activation attribute shouldn't have any effect on the > singleton attribute. the effect I have when I deploy more than one of > these Composer (all different types). > > I have another place where I end up with to many different instances > of singletons, but before digging into that I wanted to find out, if I > understand the concept of singleton within the container hierachy of a > block correctly. What you expecting to happen should be happening. I'm going to put together a testcase asap and see what is happening. Cheers, Steve. > > > with best wishes Kristian > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org > For additional commands, e-mail: dev-help@avalon.apache.org > > > -- Stephen J. McConnell mailto:mcconnell@apache.org http://www.osm.net Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org