Return-Path: Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm Delivered-To: mailing list axis-user@xml.apache.org Received: (qmail 26566 invoked from network); 7 May 2002 22:31:28 -0000 Received: from out011pub.verizon.net (HELO out011.verizon.net) (206.46.170.135) by daedalus.apache.org with SMTP; 7 May 2002 22:31:28 -0000 Received: from verizon.net ([151.200.238.69]) by out011.verizon.net (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with ESMTP id <20020507223134.FRXH16273.out011.verizon.net@verizon.net> for ; Tue, 7 May 2002 17:31:34 -0500 Message-ID: <3CD8576D.5020507@verizon.net> Date: Tue, 07 May 2002 18:38:37 -0400 From: Lyndon Durham User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: axis-user@xml.apache.org Subject: Re: threads, etc. in application scoped service References: <5.0.1.4.2.20020507155200.00af7878@andrewv.mail.iastate.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N If your running your service a servlet container implemented server, then you service is accessible by multiple clients making multiple simultaneous requests to your application service. Race conditions or threading issues only become a factor when your service accesses resource outside the container or web server e.g. a Table in a Database or some other resource. This why Transaction Management and connection pooling implementations are advocated when building applications.