Disconnected rowset CachedRowSet from a select inside stored procedure?

Question

Hello everyone
I am using CachedRowSet returning it from a parameterised select statement and it works fine.
If I put the same select statement into a simple read-only stored procedure then I get this exception: "A result set was generated for update".
I am not trying to update the rowset in my code.
I tried to make the CachedRowSet to be read-only but it does not help, same error.
Question 1 : can a stored procedure returning a single result-set be called to populate a read-only CachedRowSet? (in a similar fashion to a CallableStatement prepareCall method with input/output parameters).
Question 2: in general is using CachedRowSet, WebRowSet, FilteredRowSet (disconnected) and JDBCRowSet (connected) something to be encouraged for future develpment or are they deprecated, or replaced by something else/better??
thank you very much in advance

Answer 1

Thank you for the initial bite.
This is for Microsoft SQL Server 2008 using Microsoft JDBC driver, type 4.0.
The T-SQL stored procedure has a single select statement in it - see inside code.
Below is the Java 6 source code (including the Java import statements, many unused at the moment), apologies for poor indendation, its a cut and paste problem.
// start of Java code
import java.io.*;
import java.sql.*;
import java.text.ParseException;
import java.text.SimpleDateFormat;
import com.microsoft.sqlserver.jdbc.*;
import com.microsoft.sqlserver.jdbc.SQLServerDriver.*;
import com.microsoft.sqlserver.jdbc.SQLServerDriver;
import java.math.BigDecimal;
import com.sun.rowset.CachedRowSetImpl;
import java.net.MalformedURLException;
import java.net.URL;
import java.sql.Connection;
import java.sql.Date;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import java.sql.Timestamp;
import java.util.Calendar;
import java.util.GregorianCalendar;
import java.util.HashMap;
import javax.sql.rowset.CachedRowSet;
import javax.sql.rowset.spi.SyncProviderException;
import javax.sql.rowset.spi.SyncResolver;
public class JdbcRowSetTesting
public static void main(String[] args)
  String connectionUrl =
  "jdbc:sqlserver://ABCDE-SERVER:1433;" +
   "databaseName=SecurityTransaction;integratedSecurity=false;user=somedbuser;password=somesortofpassword";
  Connection conn = null;
  Statement sqlstmt = null;
  ResultSet rs = null;
  CachedRowSet crs = null;
   try
  conn = DriverManager.getConnection(connectionUrl);
  System.out.println("inside try block, connected");
  conn.setAutoCommit(false);
  crs = new CachedRowSetImpl();
  crs.setUrl(connectionUrl);
  crs.setReadOnly(true);
  crs.setType(ResultSet.TYPE_FORWARD_ONLY);
  crs.setConcurrency(ResultSet.CONCUR_READ_ONLY);
  System.out.println("inside try block, connected to CachedRowSet URL"); 
// this works fine:
  crs.setCommand("select ADDRESSID, COUNTRY, POSTCODE, STATE, ADDRESS1, ADDRESS2, ADDRESS3, ADDRESS4, CREATEDBY, CREATEDDATE, UPDATEDBY, UPDATEDDATE from dbo.address where ADDRESSID > ?;");
-- this does not work - the SP has  the same SELECT as above inside it:
  crs.setCommand("{ call dbo.p_testCachedJDBCRowSet (?) }");
  crs.setInt(1, 10);
  crs.execute();
   while (crs.next())
  System.out.println("" + crs.getInt("ADDRESSID") + " " +
  crs.getString("ADDRESS1"));
   catch (Exception e)
  System.out.println("inside catch block, calling Exception printStackTrace(); method now:");
  e.printStackTrace();
   finally
  System.out.println("inside finally block");
   if (rs != null) try { rs.close(); } catch(Exception e) { e.printStackTrace(); }
   if (sqlstmt != null) try { sqlstmt.close(); } catch(Exception e) { e.printStackTrace(); }
   if (conn != null) try { conn.close(); } catch(Exception e) { e.printStackTrace(); }
return;
// end of Java source code