You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Kathey Marsden <km...@Sourcery.Org> on 2005/01/12 22:22:33 UTC

Accessing JDBC30 methods with jdk131

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I am working on some issues with XA and Network Server and jdk131.
Network Server needs to access some of the JDBC30 methods such as
PreparedStatement.getParameterMetaData() to send parameter information
back to the client.

Network Server uses reflection to access these methods. For example, it
needs to access the parameterMetaData call for regular connections from.
	EmbedPreparedStatement
	EmbedPreparedStatement30

and for XA Connections from
	BrokeredPreparedStatement
	BrokeredPreparedStatement30

(Currently there is a method getEmbedParameterSetMetaData() in
EmbedPreparedStatement which is the same thing as
EmbedPreparedStatement30.getParameterMetaData() which is what Network
Server calls for regular connections so we have access from jdk131.)

Currently the options I see for providing access to the JDBC30 methods
for XA are.
1) Get rid of the *30 Classes and just put the JDBC30 methods in the
BrokeredPreparedStatement and EmbedPreparedStatement classes.

2) Import the Embed* classes into the Brokered* classes and create
methods like getEmbedParameterSetMetaData there. Really messy because
currently the Brokered* classes don't import any internal classes at all.


Option 1 seems really preferable to me but  I was wondering what we
would be giving up by getting rid of the *30 classes.   Any thoughts on
these or other options?

Thanks

Kathey





-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB5ZTVG0h36bFmkocRAj6AAKCC6NM+r7Xh7bdxC5PR4PPvyFQqBgCgrYmy
ANQoFk/11O2J7f9X34foqsw=
=AKd+
-----END PGP SIGNATURE-----