OK, it looks like if my SoapBindingSkeleton is an implementation of ServiceLifecycle then JavaProvider.java will call a destroy() method when a session is ended.
My question: Is there a way to cause wsdl2java (et al) to create my skeleton with this interface without resorting to manually changing the code whenever we regen the skeleton? Is there a better way to do this? Is there a way to register a AxisHTTPSessionListener so I can get notified? Wayne Johnson <[EMAIL PROTECTED]> wrote: I have an Axis WSDD service that needs to tell if and when a client disconnects, so that we can clean up session information. I can't simply rely on a logoff method getting called, because the disconnect might be based on external factors, like loss of network, etc. We also appear to have a problem with the client timing out. Is there a way to detect when this happens before we try to send the next packet? Or of preventing timeouts? Thanks. --- Wayne Johnson, | There are two kinds of people: Those 3943 Penn Ave. N. | who say to God, "Thy will be done," Minneapolis, MN 55412-1908 | and those to whom God says, "All right, (612) 522-7003 | then, have it your way." --C.S. Lewis --------------------------------- Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains. --- Wayne Johnson, | There are two kinds of people: Those 3943 Penn Ave. N. | who say to God, "Thy will be done," Minneapolis, MN 55412-1908 | and those to whom God says, "All right, (612) 522-7003 | then, have it your way." --C.S. Lewis --------------------------------- No need to miss a message. Get email on-the-go with Yahoo! Mail for Mobile. Get started.
