persistent web service

["Marcia Perry (DSD staff)" <MP...@lbl.gov>]

Hi,

I'm wondering if a w.s deployed under Axis (and running in Tomcat)
can have persistence such that it can receive event notifications
asynchronously over a fairly long period of time.  For ex., suppose
I want to this:
	public String foo() {
	  while (long_standing_condition_is_true) {
		 // receive notification
		 return "return_string";
	  }
	  return "blah";
         }

And I want to invoke foo() from somewhere else by sending the
SOAP message defined for the operation foo in this web service's
WSDL.  Will I get a new instance of this web service for each
invocation?  Can I arrange that a designated instance of this
web service is the recipient of the notifications?
While servlets can use HTTP session Ids and w.s. aggregation
implementations such as BPEL use mechanisms like WS-Address or 
correlation sets to match replies to responses, does Axis and/or
Tomcat support something similar for web services?

-- marcia
----------------------------------------------------------------
Marcia Perry                            MPerry@lbl.gov
Lawrence Berkeley National Laboratory   WORK#  (510) 486-6786
1 Cyclotron Road                        FAX#   (510) 486-6363
Berkeley, CA 94720     			MS: 50A-3111