OPENIG-28 Avoid out-of-bound alike errors when prepared statement is not parameterized

Trying to fill a non-existent prepared-statement placeholder results in a
SQLException (`Invalid column index` for Oracle, some other for MySQL, ...),
so we simply avoid theses errors by ignoring extra parameters.

We also output meaningful (I hope) warnings for both extra parameters
and un-valued placeholders.

git-svn-id: https://svn.forgerock.org/openig/trunk@673 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
OPENIG-85 OPENIG-28 Use ResultSet.next() instead of ResultSet.first()

The JDBC spec states that PreparedStatement created through Connection.prepareStatement(String)
have the FORWARD_ONLY type. A forward only statement may not implement the first() method (does
not make sense to go back to the first row when you can only move forward).

So, it's safer to use ResultSet.next().

git-svn-id: https://svn.forgerock.org/openig/trunk@674 dbb9e58e-28e6-4ce0-90e8-f11d9605b710