[
http://jira.jboss.com/jira/browse/JBAS-2696?page=comments#action_12344102 ]
Adrian Brock commented on JBAS-2696:
------------------------------------
It's not done, compare the cached (mc.prepare...)
public PreparedStatement prepareStatement(String sql, int resultSetType, int
resultSetConcurrency)
throws SQLException
{
checkTransaction();
try
{
return new WrappedPreparedStatement(this, mc.prepareStatement(sql, resultSetType,
resultSetConcurrency));
}
catch (Throwable t)
{
throw checkException(t);
}
}
with the non-cached (mc.getConnection().prepare...)
public PreparedStatement prepareStatement(String sql, int autoGeneratedKeys) throws
SQLException
{
checkTransaction();
try
{
return new WrappedPreparedStatement(this,
mc.getConnection().prepareStatement(sql, autoGeneratedKeys));
}
catch (Throwable t)
{
throw checkException(t);
}
}
Support other prepare[Statement|Call] methods
---------------------------------------------
Key: JBAS-2696
URL:
http://jira.jboss.com/jira/browse/JBAS-2696
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: JCA service
Reporter: Adrian Brock
Add support for other prepare[Statement|Call] methods.
This will be more difficult since they are JDK1.4/JDBC3 which might not necessarily
be supported by all drivers. e.g. result set Holdability.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira