Right. Have been a little dumb - had some cases where this seemed to be happening. Got some errors in tomcat logs from users clicking stop part way through somthing. On closer inspection it is because the action is outputing a pdf itself directly.
Now knowing that the action will always complete i'm satisfied it will work. I think i'll run the mail sending commands in a new thread to hide any delays from the user. Thanks for your help, Daniel. -----Original Message----- From: Joe Hertz [mailto:[EMAIL PROTECTED] Sent: 18 May 2004 17:52 To: 'Struts Users Mailing List' Subject: RE: sending emails from a struts app > This is what i want to acheive. I cant have the user > submitting a request, and then stopping it part way through. This is what you get. The browser simply says, "Do this". And you do. There is no Mechanism for the user to say, "No! Stop! Don't!". You may never get the request if there is a network problem, but that isn't what you seem to be worried about. The browser might give up (stop button, etc) before getting the response, and if you were writing the resultant HTML to the response yourself, then you'd have to handle the exception that could result from connection being gone, but in Struts you'd use JSP and so you wouldn't have to. If youre worried about the user clicking a button, "stopping", and since they'd be on the same page, they could then press the same button (re-executing the same code) and getting you into some bad state, look at using tokens. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
