RE: How is catch{} code handled

2004-01-02 Thread George Sexton
3 438 9585 -Original Message- From: Merrill Cornish [mailto:[EMAIL PROTECTED] Sent: Friday, January 02, 2004 1:00 PM To: Tomcat Users List Subject: Re: How is catch{} code handled George, >Unfortunately, your logic is flawed. > > Yes, that's very clear at this point. :-

Re: How is catch{} code handled

2004-01-02 Thread Merrill Cornish
George, Unfortunately, your logic is flawed. Yes, that's very clear at this point. :-) I understand that the sendRedirect() does NOT terminate the execution flow that it is in. That's why I follow each one with a return. However, I think I now recognize my problem. In my mind, I've always

RE: How is catch{} code handled

2004-01-02 Thread Craig Berry
Merrill Cornish [mailto:[EMAIL PROTECTED] wrote... > Why did main servlet processing appear to continue (allowing the > second sendRedirect() to cause a problem) after the exception was > triggered? Processing of a catch block does not terminate processing of the surrounding method. In other wo

Re: How is catch{} code handled

2004-01-02 Thread Rhino
I haven't got a clue what your problem is. Your explanation is entirely verbal and would really benefit from code snippets to make it clearer. I just can't get a clear mental picture of what you did with your code. I can't presume to speak for anyone else but I wouldn't be surprised if others felt

RE: How is catch{} code handled

2004-01-02 Thread George Sexton
Unfortunately, your logic is flawed. The major flaw is that sendRedirect() does not terminate processing of the servlet. IOW, this is happening: Servlet Invoked Sub-Routine Invoked SQLException Generated Exception Caught Send-Redirect to Err