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.
Best regards.
Oystein Grovlen - Sun Norway wrote:
TomohitoNakayama wrote:
> Hello.
>
> Thank you for your kindness :)
>
> What is needed is calling method which was introduced in JDBC 4.0
> from NetworkServer to utilize JDBC 4.0 feature in Engine.
> Concretely,the method is PreparedStatement#setBinaryStream(int,
> java.io.InputStream).
>
http://download.java.net/jdk6/docs/api/java/sql/PreparedStatement.html#setBinaryStream(int,%20java.io.InputStream)
>
>
> What is important is that JDBC 4.0 is optional and
> implementation to utilize the feature of it should be appropriately
> placed in code of NetworkServer
> in order to keep compatibility for previous spec in NetworkServer.
>
If I understand you correctly the issue is:
- When using Layer B streaming, you want the Network Server to be
able to use the new JDBC 4 methods for lengthless streaming.
- The problem is that the JDBC 4 methods is not directly available
to the NetworkServer if using older run-time libraries (e.g., Java
SE 5).
Since the implementation of the JDBC 4 methods will be part of
derby.jar regardless of which JVM you are running on, I would guess it
is just a question of how to make them available to the network
server.
--
/*
Tomohito Nakayama
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Naka
http://www5.ocn.ne.jp/~tomohito/TopPage.html
*/
