O (a) PreparedStatement

O (b) ParameterizedStatement

O (c) ParameterizedStatement and CallableStatement

O (d) All kinds of Statements (i.e. which implement a sub interface of Statement)

O (a) By invoking the method get (..., String type) on the ResultSet, where type is the database

O (b) By invoking the method get (..., Type type) on the ResultSet, where Type is an object

O (c) By invoking the method getValue (...), and cast the result to the desired java type.

O (d) By invoking the special getter methods on the ResultSet: getString (...), get Boolean (...),

O (a) By making use of the InsertStatement, DeleteStatement or UpdateStatement classes

O (b) By invoking the execute(...) or executeUpdate(...) method of a normal Statement object

O (c) By invoking the executeInsert(...), executeDelete(...) or executeUpdate(...) methods of

O (d) By making use of the execute(...) statement of the DataModificationStatement object

O (a) You must catch the checked SQLException which is thrown by the method which executes

O (b) You must catch the unchecked SQLWarningException which is thrown by the method

O (c) You must invoke the getWarnings() method on the Statement object (or a sub interface

O (d) You must query the ResultSet object about possible warnings generated by the database

O (a) A DataSource is the basic service for managing a set of JDBC drivers

O (b) A DataSource is the Java representation of a physical data source

O (c) A DataSource is a registry point for JNDI-services

O (d) A DataSource is a factory of connections to a physical data source

O (a) This means that the ResultSet is insensitive to scrolling

O (b) This means that the Resultset is sensitive to scrolling, but insensitive to updates, i.e. not

O (c) This means that the ResultSet is sensitive to scrolling, but insensitive to changes made

O (d) The meaning depends on the type of data source, and the type and version of the driver

O (a) Yes, but only if you call the method openCursor() on the ResultSet, and if the driver and

O (b) Yes, but only if you indicate a concurrency strategy when executing the statement, and

O (c) Yes, but only if the ResultSet is an object of class UpdateableResultSet, and if the driver

O (d) No, ResultSets are never updateable. You must explicitly execute DML statements (i.e.

[_] [a] A transaction is a set of successfully executed statements in the database

[_] [b] A transaction is finished when commit() or rollback() is called on the Connection object,

[_] [c] A transaction is finished when commit() or rollback() is called on the Transaction object

[_] [d] A transaction is finished when close() is called on the Connection object.

O (a) By asking a Transaction object to your Connection, and calling the method begin() on it

O (b) By asking a Transaction object to your Connection, and setting the autoCommit property

O (c) By calling the method beginTransaction() on the Connection object

O (d) By setting the autoCommit property of the Connection to false, and execute a statement

O (a) Dirty reads, non-repeatable reads and phantom reads can occur

O (b) Dirty reads are prevented; non-repeatable reads and phantom reads can occur

O (c) Dirty reads and non-repeatable reads are prevented; phantom reads can occur

O (d) Dirty reads, non-repeatable reads and phantom reads are prevented

[_] [a] Using the cursor technique is currently the only possible way to change the data in the

[_] [b] Insert statements are not supported when using cursors.

[_] [c] Only scrollable updateable ResultSets can use this approach to change the data in the

[_] [d] The name of the cursor is specified by the setCursorName(String name) method the

O (a) Call method execute() on a CallableStatement object

O (b) Call method executeProcedure() on a Statement object

O (c) Call method execute() on a StoredProcedure object

O (d) Call method run() on a ProcedureCommand object

O (a) the method close() does not exist for a ResultSet. Only Connections can be closed.

O (b) the database and JDBC resources are released

O (c) you will get a SQLException, because only Statement objects can close ResultSets

O (d) the ResultSet, together with the Statement which created it and the Connection from

O (a) The row you are positioned on is deleted from the ResultSet, but not from the database.

O (b) The row you are positioned on is deleted from the ResultSet and from the database

O (c) The result depends on whether the property synchonizeWithDataSource is set to true or

O (d) You will get a compile error: the method does not exist because you can not delete rows

[_] [a] To create a batch of insert and update statements, you create an object of type Batch,

[_] [b] Batch insert and updates are only possible when making use of parameterized queries.

[_] [c] To do a batched update/insert, you call addBatch(String statement) on a Statement

[_] [d] To execute a batched update/insert, you call the executeBatch() method on a Statement

O (a) DDL statements are treated as normal sql statements, and are executed by calling the

O (b) To execute DDL statements, you have to install additional support files

O (c) DDL statements can not be executed by making use of JDBC, you should use the native

O (d) Support for DDL statements will be a feature of a future release of JDBC

a)Locale

b)ResourceBundle

c)Country

d)Language

1) File container.jsp will compile if the directive page comes before the directive include

2) File container will compile and when executed it will show:”Hello”.

3) File container.jsp will compile if the errorPage in container.jsp is the same as in file included.jsp.

4) File container.jsp will compile if instead of directive include () it is used the action include ()

1) It is necessary to implement TagExtraInfo interface.

2) You have to insert into the tag element of the taglib descriptor file an entry for tei-class element.

3) The interface you have to implement has a method called getVariableInfo.

4) None of the above.

1) It won't compile.

2) It is a valid jsp line and it will print the variable called name.

3) It will compile but it will always produce null as the output.

4) It will work if you create a javabean class with only one variable of type java.lang.String.