Return-Path: Delivered-To: apmail-xml-axis-user-archive@xml.apache.org Received: (qmail 68222 invoked by uid 500); 25 Jul 2002 15:49:38 -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 68211 invoked from network); 25 Jul 2002 15:49:38 -0000 X-Authentication-Warning: cslin042.leeds.ac.uk: johnh owned process doing -bs Date: Thu, 25 Jul 2002 16:49:10 +0100 (BST) From: J Hodrien X-X-Sender: To: Subject: Finalizing web services Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Status: O X-Status: X-Keywords: X-UID: 780 Is there a method that is guaranteed to be called on a web service as it is culled? With servlets I'm under the impression that you have init and destroy methods, but I haven't found the equivalent with a web service. Finalize can't be trusted to be called, so I wasn't quite sure where to place code that is required to save state between server restarts. It's hard to work around it since the service *has* to run with application scope. Thanks a lot, jh -- "It is always easier to fight for ones principles than to live up to them." -- Alfred Adler