CreateCallableStatement

Question

I am a new user to JDeveloper and am working through the tutorial on calling a stored PL/SQL procedure. All the info from the Tutorial seems to be working fine. I modified the procedure so that it would have an IN OUT parameter instead of just IN parameters because I wanted to see if it would pass back data successfully too.
In doing this I ran into some datatype problems. I have figured out how to fix the problems but I do not know why I had to fix them this way. Here is the code from the Tutorial:
public void doDML(int operation, TransactionEvent e) {
// Don't call the superclass. This procedure handles only updates
//super.doDML(operation, e);
CallableStatement stmt = null;
// ONLY Perform updates, this Entity won't allow inserts/deletes.
if (operation == DML_UPDATE)
// Prepare JDBC CallableStatement with the Stored Procedure Call
String updateStr = "{call update_inventory(?,?,?,?)}";
stmt = getDBTransaction().createCallableStatement(updateStr, 1);
try
// Bind the Statement Parameters and Execute this Statement
stmt.setString(1, getId().toString());
stmt.setString(2, getDescription().toString());
stmt.setString(3, getPrice().toString());
stmt.setString(4, getOnhand().toString());
stmt.registerOutParameter(4, Types.VARCHAR);
stmt.execute();
System.out.println("OnHand: " + stmt.getString(4));
catch (Exception ex)
throw new oracle.jbo.JboException(ex);
finally
try
stmt.close();
catch (Exception nex)
I added the 'registerOutParamater' line and the 'System.out.println' statement. The Out parameter I am registering is a NUMBER colum in the database. So, I had it as NUMERIC in the registerOutParameter statement. I was getting the ArrayOfOutOfBoundsException error all the time and I noticed that when I would update the form and type '100' in the field it would get stored in the database as '-4.6E-10' or something like that...hence producing the error.
I finally realized that i had to register the OutParameter as a VARCHAR b/c in the above statements it is being passed in as a String. I tried doing the set command as setInt instead of setString but got an error that createCallableStatement does not accept that type of argument.
Could someone please explain to me why these are all being converted to strings to pass into the procedure and why my out parameter must then also be a string when it is a NUMBER column in the database? I am very confused by this. All the procedure in the database does is a simple update statement....there is no data conversion in the database so I am really confused about the string types. Obviously OnHand and Price are NUMBER columns in the database.
Thanks for your help!
null

Answer 1

Can you use the approach mentioned in (use cs.setObject())
ADF Developer's Guide: http://download.oracle.com/docs/cd/E15523_01/web.1111/b31974/bcadvgen.htm#sm0297
Section 37.5.4 How to Call Other Types of Stored Procedures
Code snippet:
*public Date callProcWithOutArgs(Number n, String v) {*
CallableStatement st = null;
*try  {*
*// 1. Define the PL/SQL block for the statement to invoke*
String stmt = "begin devguidepkg.proc_with_out_args(?,?,?); end;";
*// 2. Create the CallableStatement for the PL/SQL block*
st = getDBTransaction().createCallableStatement(stmt,0);
*// 3. Register the positions and types of the OUT parameters*
st.registerOutParameter(2,Types.DATE);
st.registerOutParameter(3,Types.VARCHAR);
*// 4. Set the bind values of the IN parameters*
st.setObject(1,n);
st.setObject(3,v);
*// 5. Execute the statement*
st.executeUpdate();
*// 6. Create a bean to hold the multiple return values*
DateAndStringBean result = new DateAndStringBean();
*// 7. Set value of dateValue property using first OUT param*
result.setDateVal(new Date(st.getDate(2)));
*// 8. Set value of stringValue property using 2nd OUT param*
result.setStringVal(st.getString(3));
*// 9. Return the result*
return result;
*} catch (SQLException e) {*
throw new JboException(e);
*} finally {*
*if (st != null) {*
*try {*
*// 10. Close the JDBC CallableStatement*
st.close();
catch (SQLException e) {}
Thanks,
Navaneeth