Hello.
Reading the code ( BaseMonitor.java, modules.properties,
InternalDriver.java and so on ),
it seems that possible class of engine is different between running
environment ...
Then, I think it is needed to consider when the class is not expected class.
Best regards.
Knut Anders Hatlen wrote:
TomohitoNakayama <[EMAIL PROTECTED]> writes:
Hello.
Thank you for your comment :)
I think you understood what the issue is.
I understand your idea as using module of Engine where JDBC4.0 feature
is implemented
directly rather than via JDBC interface from NetworkServer.
I take the idea in consideration.
The network server already does this for some JDBC 3.0 methods that it
needs even when the JVM only supports JDBC 2.0. The methods are
defined in interfaces starting with Engine (for instance,
EngineStatement and EnginePreparedStatement). When the network server
needs to call one of those methods, it casts the Statement object to
an EngineStatement.
--
/*
Tomohito Nakayama
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Naka
http://www5.ocn.ne.jp/~tomohito/TopPage.html
*/
