exception-handling

When aborting the execution of a thread I'm always doubting between a graceful exit with an event handler like this: int result = WaitHandle.WaitAny(handles); if (result = WAIT_FINALIZE) FinalizeAndExit(); and using the event to signal the thread it must terminate or just handling the ThreadAbortException to finalize the thread... try { // Main execution } catch(ThreadAbortException e) { // FinalizeAndExit(); } finally { } I'm usually inclined to use the ThreadAbortException approach since it can be handled but it is re-raised at the end of the catch block, and it also avoids the thread from

I want to implement custom exception handling in my library so that I know where an exception occurred, so I am doing this: try { DoSomething(); } catch(Exception ex) { //LibraryException refers to any exception in the libraries exception hierarchy throw new LibraryException(ex.Message, ex); } Should this be avoided? Does it have any performance implications? What are the implications of catching, nesting and re-throwing exceptions? The only potential problem is that you're catching a non-specific Exception , so not conforming to the exception handling guidelines . One of the following would

I am making an ajax submit using Primefaces but I am having trouble linking my server side message with my ajax request. Supposed I have this button that calls an action. In my managed bean, do I need to raise an exception? How do I pass this message into my ajax request public void checkout(ActionEvent event){ if(expression){ throw new CustomException("Account balance is not enough!"); } } public class CustomException extends RuntimeException { public CustomException(String message) { super(message); } } How do I handle this case? Will my onerror javascript method be able to handle this? Also