This is a long shot, but is there a way to catch specific SQL exceptions that are caused due to specific issues.
More specifically, the SQL exceptions may be caused due to many reasons and the SQLException.getState() method can be used to find the XOPEN constant. Then, I can write specific handler code to handle each subtype representing each XOPEN constant. My question is: has someone already done some work in this area (in the open source world), and I could build upon the classes? I will be working on an open source initiative of our company, so I will be able to contribute back any library that I build on top of that. My instinct is that someone out there has already coded the concrete subclasses of SQLException (for different error types) or has found sufficient reasons that subclassing is not required. In case I have to do this myself, I will still be able to contribute the classes, so if you are merely interested, let me know. Rich Armstrong Genetics Software http://www.kromosoft.com =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
