Differentiating between same exception thrown from 2 different methods

Question

Suppose I have a class CodeDAO which has 2 methods who both throw SQLException
public int getLocationCode(String locationName) throws SQLException;
public int getDepartmentCode(String departmentName) throws SQLException;Now I have a business method in which I have to use both of the above DAO methods.
public int process() {
   try {
      CodeDAO codeDAO = new CodeDAO();
      int locationCode = codeDAO.getLocationCode("NJ");
      int departmentCode = codeDAO.getDepartmentCode("Sales");
   catch (SQLException e) {
}If SQLException is thrown how will I know if it is thrown by the getLocationCode method or getDepartmentCode method?
What are the different choices I have in differentiating between same exception thrown from different methods? And which choice do you guys prefer?
Thanks

Answer 1

srhcan wrote:
maheshguruswamy wrote:
srhcan wrote:
gimbal2 wrote:
baftos wrote:
Put each method invokation in its own try/catch block.Or in fact not use SQLException, but exceptions that are unique.So each DAO method has its own exception?
public int getLocationCode(String locationName) throws GetLocationCodeException;
public int getDepartmentCode(String departmentName) throws GetDepartmentCodeException;would not that means I have to create a lot of exception classes?
Edited by: srhcan on Aug 9, 2012 2:54 PMLet me ask you this, what do you plan to do in the catch block? Do some sort of recovery? rollback? If it is just for logging purposes, I am pretty sure the exception message will give you enough information to find out where the error was.* I would like to give user a specific message based on which method fails. So if getLocationCode("NJ") fails the message can be: Unable to find code for Location "NJ". And if getDepartmentCode("Sales") fails the message can be: Unable to find code for Department "Sales".
* I would like to print the exception's stacktrace in the log file.
* I may do a rollback depending on if its an INSERT/UPDATE/DELETE statement.Well, in that case why not log it in the DAO methods themselves...inside getLocationCode and getDepartmentCode. Instead of trying to do the recovery/logging in the process method, do it in the individual dao methods. The calling classes should not be responsible for logging/recovery etc. It should be done in the DAO classes themselves and the DAO method should return an appropriate message/code to the consumer tier classes indicating the status of the transaction. Just my 0.02$.