Just use a debugging version of the driver. Many JDBC vendors provide a regular and debug version, with the debug version outputting the SQL statements. Also, its possible your current driver will output the SQL if you add some config parameters to the driver connection string. I don't recommend swapping the DebuggableStatement method for 2 reasons- you have to refactor (then later unfactor) your code to use it, and there's all ready a solution available by most, if not all, JDBC drivers. I take issue with JavaWorld post in that it invents a solution to a problem that all ready has a better solution available, one that doesn't require you to change your code.

If all else falls you can turn on tracing on the database server and monitor the queries on that end.

I have also considered advising the debugging driver, but that does not output the sql statement with the bind parameters embedded, does it? That was what the OP was asking.
If the debugging driver does that, than I am willing to revoke my advise .