Boiler Plating Database Resource Cleanup With Execute Around Method ACCU London February 2009 ACCU Conference April 2009 Validus 8 Thorpe Road Norwich NR1 1RY Paul Grenyer Senior Software Engineer

Agenda  All About Me  The Problem (audience participation)  Execute Around Method  A solution

Speaker biography  Who am I?  My career so far  Validus-IVC and what I do there

The Problem

Audience Participation 1 Write some JDBC code to execute the following update statement: UPDATE SERVICES SET URL=" WHERE NAME = ' ' Key concept: Connection User

Creating a Connection try { Class.forName(DRIVER); final Connection con = DriverManager.getConnection( CONNECTION_STRING, USERNAME, PASSWORD); con.setCatalog(DATABASE); // Use connection } catch(ClassNotFoundException e) { // handle error } catch(SQLException e) { // handle error }

Creating and using a Statement... final Statement stmt = con.createStatement(); try { stmt.execute(SQL); } finally { try { stmt.close(); } catch(SQLException e) { // handle error }...

Wouldn't it be nicer if you could do this? try { final ConnectionProvider cp = new ConnectionProvider(new StringConnection(DRIVER, CONNECTION_STRING).setUser(USERNAME,PASSWORD).setDatabase(DATABASE)); Query.execute( cp, "UPDATE … WHERE NAME = ' '"); } catch(Exception e) { // Report error }

Audience Participation 2 Write some JDBC code to execute the following select statement: SELECT URL FROM SERVICES and write the result to the console Key concept: Connection Value

Creating and using a Result Set... final Statement stmt = con.createStatement(); try { final ResultSet rs = stmt.executeQuery(SQL); try { while(rs.next()) { System.out.println(rs.getString("url")); } finally { try { rs.close(); } catch(Exception e) { // Handle exception }...

Wouldn't it be nicer if you could do this? try { final ConnectionProvider cp = new ConnectionProvider(new StringConnection(DRIVER,CONNECTION_STRING).setUser(USERNAME, PASSWORD).setDatabase(DATABASE)); final List urls = Query.execute( cp, "SELECT URL FROM SERVICES", new RSProcessor()); for(String url : urls) { System.out.println(url); } catch(Exception e) { e.printStackTrace(); }

Wouldn't it be nicer if you could do this? class RSProcessor extends AbstractResultSetFunction > public List read(ResultSet rs) { List result = new ArrayList (); try { while (rs.next()) { result.add(rs.getString("url")); } catch(SQLException ex) { getErrorPolicy().handleError(ex); } return result; }

Execute Around Method (EAM) “Encapsulate pairs of actions in the object that requires them, not code that uses the object, and pass usage code to the object as another object.” Kevlin Henney ?

File Writer

public interface WriterUser { void use(Writer writer) throws IOException ; } public class FileWriterProvider { private final String filename; public FileWriterProvider(String filename) { this.filename = filename; } public void provideTo(WriterUser user) throws IOException { final FileWriter writer = new FileWriter(filename); try { user.use(writer); } finally { writer.close(); }

new FileWriterProvider("out.txt").provideTo(new WriterUser() public void use(Writer writer) throws IOException { writer.write("Execute Around Method!"); } });

Execute Around Method (EAM) “Using an object to manage a resource and provide it to another object to use”

The Solution  Resource management  Providers (inc. connection factory) & Users  Error handling

Resource Management Resources to manage:  Connection  Statement  ResultSet Each must be:  Acquired  Used  Cleaned-up

Connection Provider > Statement Provider > ResultSet Provider >

Connection Provider The concept of a connection provider was suggested to me by Adrian Fagg. The idea is that:  A single class is responsible for acquiring a connection  Providing it to another class for use  Releasing it again Execute Around Method!

Connection Provider

Connection Factory Interface public interface ConnectionFactory { Connection connect(); void disconnect(Connection con); } Why have a connection factory?  On demand connection  Connection pool  Existing connection  Custom connection

Connection Factory: disconnect public abstract class AbstractConnectionFactory implements ConnectionFactory public void disconnect(Connection con) { if (con != null) { try { con.close(); } catch(final SQLException ex) { // To do }  A Connection can be created any number of ways.  A Connection is usually closed in the same way.

Connection Factory: connect public Connection connect() { Connection con = null; try { Class.forName(driver); con = DriverManager.getConnection( connectionString, username, password); } catch(ClassNotFoundException ex) { // To do } catch(SQLException ex) { // To do } return con; }

Connection Provider: Construction public final class ConnectionProvider { private final ConnectionFactory conFactory; public ConnectionProvider(ConnectionFactory conFactory) { this.conFactory = conFactory; }

Key Concepts User: An object that uses a JDBC resource, but doesn’t return a value. public interface ConnectionUser { void use(Connection con); } Value User: An object that uses a JDBC resource and returns a value. public interface ConnectionValue { T fetch(Connection con); }

Connection User Interface public interface ConnectionUser { void use(Connection con); }  Uses the connection  Does not return a value!

Connection Provider: User public void provideTo( ConnectionUser user ) { final Connection con = conFactory.connect(); try { user.use(con); } finally { conFactory.disconnect(con); }  Uses Finally for Each Release Pattern to:  Create a Connection from the factory  Passes the Connection to the user  Closes Connection

Connection Value User public interface ConnectionValue { T fetch(Connection con); } Like the ConnectionUser, but:  Fetch method has a return type  Return type is a generic parameter

Connection Provider: Value User public T provideTo( ConnectionValue valueUser ) { final Connection con = conFactory.connect(); T result = null; try { result = valueUser.fetch(con); } finally { conFactory.disconnect(con); } return result; }  Uses Finally for Each Release pattern to:  Create a Connection from the factory  Passes the Connection to the user and stores the result  Closes connection  Passes the result back.

Statement Provider

Statement User and Value User public interface StatementUser { void use(Statement stmt); } public interface StatementValue { T use(Statement stmt); }

Statement Provider: Value User public T provideTo( StatementValue valueUser ) { T result = null; try { final Statement stmt = con.createStatement(); try { result = valueUser.use(stmt); } finally { try { stmt.close(); } catch(SQLException ex) { // To do } catch(SQLException ex) { // To do } return result; }

Result Set Provider

ResultSetFunction public interface ResultSetFunction { T read(ResultSet rs); }  Iterates through RecordSet.  Returns result.

ResultSet Provider public T provideTo(ResultSetFunction fetcher) { T result = null; try { final ResultSet rs = stmt.executeQuery(sql); try { result = fetcher.read(rs); } finally { try { rs.close(); } catch(Exception ex) { // To do } catch(SQLException ex) { // To do } return result; }

Connection Provider > Statement Provider > ResultSet Provider > Putting It All Together.

Error Policy A common error policy allows the client to decide how to handle errors: public interface ErrorPolicy { void handleError(Exception ex) void handleCleanupError(Exception ex) }  Clean-up exceptions could be handled differently  May be logged, rather than re-thrown  Decision can be made by the client

public T provideTo( StatementValue valueUser ) { T result = null; try { final Statement stmt = con.createStatement(); try { result = valueUser.use(stmt); } finally { try { stmt.close(); } catch(SQLException ex) { // handle clean-up exception } catch(SQLException ex) { // Handle exception } return result; }

To Check or Not To Check Checked Exceptions  Interface methods can throw Exception.  Interface methods can throw a custom exception that all checked exceptions must be translated into. public interface ErrorPolicy { void handleError(Exception ex) throws Exception; void handleCleanupError(Exception ex) throws Exception; } public interface ErrorPolicy { void handleError(Exception ex) throws CustomException; void handleCleanupError(Exception ex) throws CustomException; }

To Check or Not To Check Runtime Exceptions  The implementer of the interface is forced to translate checked exceptions to runtime exceptions. public interface ErrorPolicy { void handleError(Exception ex) void handleCleanupError(Exception ex) }

Default Error Policy public class DefaultErrorPolicy implements ErrorPolicy { private Exception firstException = public void handleCleanupError(Exception ex) { handleError(ex); public void handleError(Exception ex) { if (firstException == null) { firstException = ex; throw new RuntimeException(ex); }

Error Policy User public interface ErrorPolicyUser { void setErrorPolicy(ErrorPolicy errorPolicy); }  All classes that use an ErrorPolicy must implement the ErrorPolicyUser interface.  The ErrorPolicyUser is used by providers to pass an ErrorPolicy to its User s and Value s (dependency injection).  All User s and Value s must therefore be an ErrorPolicyUser.

public interface ConnectionFactory extends ErrorPolicyUser { Connection connect(); void disconnect(Connection con); } public interface ConnectionUser extends ErrorPolicyUser { void use(Connection con); } public interface ConnectionValue extends ErrorPolicyUser { T fetch(Connection con); } public interface StatementUser extends ErrorPolicyUser { void use(Statement stmt); } public interface StatementValue extends ErrorPolicyUser { T use(Statement stmt); } public interface ResultSetFunction extends ErrorPolicyUser { T read(ResultSet rs); }

public final class StatementProvider { public void provideTo( StatementUser user ) { user.setErrorPolicy(errorPolicy); try { final Statement stmt = con.createStatement(); try { user.use(stmt); } finally { try { stmt.close(); } catch(SQLException ex) { errorPolicy.handleCleanupError(ex); } catch(SQLException ex) { errorPolicy.handleError(ex); }

Common Error Policy User public abstract class AbstractErrorPolicyUser implements ErrorPolicyUser { private ErrorPolicy errorPolicy = new DefaultErrorPolicy(); protected ErrorPolicy getErrorPolicy() { return errorPolicy; public void setErrorPolicy(ErrorPolicy errorPolicy) { this.errorPolicy = errorPolicy; }  The CommonErrorPolicyUser provides a common:  ErrorPolicy set method  ErrorPolicy reference  ErrorPolicy accessor

Composition  Unnecessary ErrorPolicyUser reference.  Unnecessary set/get ErrorPolicy methods implemented in ConcreteUser.

Inheritance  ConcreteConnection inherits set/get methods for free.  ConecreteConnection IS-A ErrorPolicyUser

public class Execute extends AbstractErrorPolicyUser implements StatementUser public void use(Statement stmt) { try { for(String s : sql) { stmt.execute(s); } catch(SQLException ex) { getErrorPolicy().handleError(ex); }

Sorted!

Connection Provider > Statement Provider > ResultSet Provider >

Reminder try { final ConnectionProvider cp = new ConnectionProvider(new StringConnection(DRIVER,CONNECTION_STRING).setUser(USERNAME, PASSWORD).setDatabase(DATABASE)); final List urls = Query.execute( cp, "SELECT URL FROM SERVICES", new RSProcessor()); for(String url : urls) { System.out.println(url); } catch(Exception e) { e.printStackTrace(); }

Reminder class RSProcessor extends AbstractResultSetFunction > public List read(ResultSet rs) { List result = new ArrayList (); try { while (rs.next()) { result.add(rs.getString("url")); } catch(SQLException ex) { getErrorPolicy().handleError(ex); } return result; }

Anymore questions? See you in the bar… Validus 8 Thorpe Road Norwich NR1 1RY Paul Grenyer Senior Software Engineer