Does CallableStatement have to be closed?

[Jian Yi]

I need to modify the following code in a way that the upper level will handle the SQLException. The original code is:

public boolean deleteALP(UserBean user,
String ALP_ALW_IDENT ,
String ALP_PROD_PRD 
) 
{
int val = 0;
CallableStatement cstmt = null;
boolean status = false; 
try{
cstmt = user.getConnection().prepareCall("{CALL CP_DBA.del_ALP_gen(?,?)}");
...
val = cstmt.executeUpdate();
if(val==0) status = true;
else status = false;
} 
catch (java.sql.SQLException ex){
ex.printStackTrace();
status = false;
}finally{
try{
if(cstmt!=null) cstmt.close();
cstmt = null;
}catch(java.sql.SQLException ex1) {}
}
return status;
}

I understand that I need to move the catch block to the upper level and declare the methods with throws SQLExeption. My question is, if SQLException is thrown at the line of "val = cstmt.executeUpdate();" then it got thrown to upper level. So the cstmt never gets closed (that's what finally block is doing). I wonder if it is ok for cstmt without being closed. What could happen? Or, is it possible that when CallableStatment::executeUpdate() throws a SQLException, it closes the statement for us automatically?
Thanks a lot,
Jenny

[Marilyn de Queiroz]

Please reply to this post