Return-Path: Delivered-To: apmail-xml-axis-user-archive@xml.apache.org Received: (qmail 81888 invoked by uid 500); 16 Aug 2002 18:20:59 -0000 Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@xml.apache.org Received: (qmail 81878 invoked from network); 16 Aug 2002 18:20:59 -0000 Message-ID: <014b01c24552$03436b20$1219570f@ranier> From: "Steve Loughran" To: References: <5.1.0.14.2.20020816112608.026e77a0@andrewv.mail.iastate.edu> <3D5D36FF.5060809@exis.com> Subject: Re: How to initialize deployed services? Date: Fri, 16 Aug 2002 11:23:23 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-MailScanner: Found to be clean X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Status: O X-Status: X-Keywords: ----- Original Message ----- From: "Colin Sampaleanu" To: Sent: Friday, August 16, 2002 10:31 AM Subject: Re: How to initialize deployed services? > Thanks. I've now gone back in the archives and found that thread, called > "Configuring a web service...", which was of some help. Too bad there > isn't a way to deploy live objects. That approach really fits some > scenarios a lot better. yeah, it would be nice. .NET remoting lets you do this, which is why it is my favourite of the two .NET stacks (the other reason is that it doesnt need IIS, which must be a good thing). Looks like a coding opportunity to me. > > Along with the servletContext, I guess the other way you could get to > live objects is via JNDI and singletons... > > It would be nice if a minimal addition was implemented, where the .wsdd > file could specify parameters to the service. Steven suggested having > the service read in a config file with a name based on the hostname, but > this is not necessarily a dependency I want to have. Being able to pass > in some param to that instance of the service to identify it would help > in a big way... my hostname based process worked in the 'when web services go bad' example as we had about 30 systems, split into 5 clusters and some dev boxes, but even then cluster-side it wasnt dynamic enough, to change a property on 4 boxes needed four edits or a reinstall. This is why I like ldap. there is the ldap boot process: how do you find your server? I am using multicast IP, a service boots saying 'who is a config server', gets the list back then goes 'who knows about me, my hostname is "foo"'?; sort of like DHCP