Partial Driver Implementation

Hi All,
My application needs to connect to a sql database, which provides a partial driver implementation. Means to say that It does not implement either DataSource or XADataSource.
But for my enterprise application, deployed on Sun One Application Server 7, I need to create a pool name, for this database.
What should be done under these circumstances.
Thanks and Regards,
Ravi.
([email protected])

Unless writing a JDBC driver is the goal of this project, I don't see this as a particularly straightforward task. The network protocol Oracle uses is proprietary, so unless you want to invest a lot of effort in reverse engineering it, you'd have to write a driver that used OCI to communicate with the database. That would require that you install the Oracle client on the application server and delve pretty deeply into the OCI API-- not a trivial task on its own.
Additionally, I doubt that the internal logic required to be able to execute stored procedures is significantly smaller than the code to do both.
Justin
Distributed Database Consulting, Inc.
www.ddbcinc.com/askDDBC

Similar Messages

  • Driver implementation in java

    Hi,
    I am working on a personal project in which i am planning to use a servlet that will call stored procedures from an oracle 9 database.
    My questions are :
    Is it logical to write and use a driver which is only capable of calling stored procedures, instead of standard JDBC driver for Oracle (to decrease memory requirements of the servlet). If so how can I find information to implement such a driver.
    Thanks.
    Volkan Erdogan

    Unless writing a JDBC driver is the goal of this project, I don't see this as a particularly straightforward task. The network protocol Oracle uses is proprietary, so unless you want to invest a lot of effort in reverse engineering it, you'd have to write a driver that used OCI to communicate with the database. That would require that you install the Oracle client on the application server and delve pretty deeply into the OCI API-- not a trivial task on its own.
    Additionally, I doubt that the internal logic required to be able to execute stored procedures is significantly smaller than the code to do both.
    Justin
    Distributed Database Consulting, Inc.
    www.ddbcinc.com/askDDBC

  • Exist SQLServer driver implement JDBC20 createStatement(ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_UPDATABLE)?

    Hello,
    I have to perform a kind of "SELECT FOR UPDATE" in a database transaction. My
    DBMS is SQLServer. I think the best approach is to use the createStatement(ResultSet.TYPE_FORWARD_ONLY,
    ResultSet.CONCUR_UPDATABLE) sentence, as this should properly work in other DBMS
    like Oracle as well.
    The problem is that the driver which is provided with WebLogic Server 6.1 beta
    (weblogic.jdbc20.pool.Driver because I am using pools) does not implement this
    sentence. What should I do to get another driver which implements that? Does it
    exist? Do I have to buy it to a third company?
    I have read dozens of messages in this newsgroup regarding JDBC20, but questions
    are usually from Oracle users. I even would not understand how to solve the problem
    if I had Oracle, I think a good explanation about all this mess is missing in
    the Weblogic documentation.
    Any help would be appreciated. Regards,
    David

    David,
    Have a look at the Merant DataDirect drivers.
    Free type 3 and 4 evals are available at www.merant.com/datadirect.
    Cheers,
    Dimitri
    "Sree Bodapati" <[email protected]> wrote in message
    news:[email protected]..
    hi david,
    MS SQL Server driver that ships with WLS does not support JDBC 2.0methods.
    You will have to use a third party driver for this.
    hth
    sree
    "David Ruana" <[email protected]> wrote in message
    news:3b681248$[email protected]..
    Hello,
    I have to perform a kind of "SELECT FOR UPDATE" in a database
    transaction.
    My
    DBMS is SQLServer. I think the best approach is to use thecreateStatement(ResultSet.TYPE_FORWARD_ONLY,
    ResultSet.CONCUR_UPDATABLE) sentence, as this should properly work inother DBMS
    like Oracle as well.
    The problem is that the driver which is provided with WebLogic Server
    6.1
    beta
    (weblogic.jdbc20.pool.Driver because I am using pools) does not
    implement
    this
    sentence. What should I do to get another driver which implements that?Does it
    exist? Do I have to buy it to a third company?
    I have read dozens of messages in this newsgroup regarding JDBC20, butquestions
    are usually from Oracle users. I even would not understand how to solvethe problem
    if I had Oracle, I think a good explanation about all this mess is
    missing
    in
    the Weblogic documentation.
    Any help would be appreciated. Regards,
    David

  • Driver implementa​tion into PID manuel-Aut​o Temp Control Example vi

    There is PID manuel-Auto Temp Control Example vi in PID tool kit. I want to use this in my system implementing of my driver. Lakeshore 336 temp. control. Please advice me how to put drivers, what to do to use this tool kit with instrument. I need direction like, change this with this, delete this and add this...
    thanks in advance....

    Dear all,
    thanks for advices. PID tutorials help me alot. yeap, 336 has already PID control itself.I downloded and installed inst.lib already and it works. The problem is my vi. I want my vi like PID tool kit vi. I mean very nice control. I am not sure that I made nice. It works, but response time, wuality, noise, and so on. If someone can interests, I can send my vi to be checked and make comment on it.
    I started to study LV in 2003. At that time I didn't know English (I am Turkish) so I couldn't find any source in my language. I tried to learn by myself following vi's. Then I left it and started working 3 weeks ago. So, I am beginner, but I could write my own high temperature controller.)
    But I would like be adviced in any case from experienced people like you.  Thanks in advance...

  • Partial Interface Implementation.....am I right?

    Hi there everyone,
    I am reading Ivor Hortons book, "Beginning Java 2 SDK 1.4 Edition". I have just got to the part where he talks about interfaces. I get interfaces, no problem.....but then he goes on about implementing some methods from an interface and not others. I quote: -
    "You can omit the implementation of one or more of the methods from the interface in a class that implements the interface, but in this case the class inherits some abstract methods from the interface so we would need to declare the class itself as abstract"
    This is what I think he means (from what I have learned so far)....
    An abstract class is a class that that declares methods without actually "filling them in"....it is assumed that this will be done by a sub-class which inherits from this super-class.
    Therefore, if you don't implement all the methods in the interface in a class, that class must also be declared as abstract, as you have methods left over that you have not implemented.
    Is this right?
    He goes on to say that because the class is an abstract class, you can't create instances of this class....unless a sub-class of this class is created that implements the remaining methods. Which seems logical, I guess.....but why would you do this? It seems to be a lot of trouble just to neglect a few methods...they have to be implemented in a sub-class anyway to "arrive at a useful class" as he puts it.
    So whats the point?
    Also (as an aside)....if you have a class that must enforce method formatting.....why would you use an interface instead of having your class inherit abstract methods from a super-class? Is is because you can only inherit from one super-class (which wouldn't be much use for sub-classes that needed to enforce certain other methods)? I understand that C++ can inherit from multiple super-classes, thus negating the need for interfaces. This seems right to me.
    How did I do? :) Any comments?
    Thank you.
    Jon

    An abstract class is a class that that declares
    methods without actually "filling them in"....
    etc....
    Is this right?Pretty much, yep.
    He goes on to say that because the class is an
    abstract class, you can't create instances of this
    class....unless a sub-class of this class is created
    that implements the remaining methods. Which seems
    logical, I guess.....but why would you do this? It
    seems to be a lot of trouble just to neglect a few
    methods...they have to be implemented in a sub-class
    anyway to "arrive at a useful class" as he puts it.
    So whats the point?When you specify the interace, let's call it Foo, you're saying what methods a class must provide if it's to call itself a Foo, but not how do provide that funcionality--that's left up to the actual implementation, as you've learned. For a given interface, there are many ways it could be implemented. However, there may be some common implementations for some of the methods that a family of implementing classes can share--a default implementation that isn't tuned and tweaked for any particular kind of use, but that does work. There may also be some methods for which no reasonable default exists, because it would be too closely tied to whatever your particular implementation is.
    For a good example of this, look at the Collections Framework in the java.util package: List, AbstractList, AbstractSequentialList, LinkedList, ArrayList. By the time you get down to either LinkedList or ArrayList, there are only a couple of methods that are left unimplemented. Those methods interact directly with the backing store--i.e. that have to access "array[ix]" for ArrayList or the linked list nodes for LinkedList, so it doesn't make sense to provide a "common" or "default" implementation. The other methods use these methods to do their work, so they don't depend on the particulars of the backing store and hence a common/default implementation is provided for them.

  • JDBC driver implementation

    Hi,
    I want to implement JDBC drivers for my mini database (that I have created for fun) so that client applications can connect to my database using any existence JDBC client. I understand that I need to implement certain interfaces - java.sql.Connection etc for this. But if someone can point me to detail specs - what needs to be done and better how it is to be done- it will be a great help. Any link to open source code is more than welcome.
    Thanks,
    Taran
    PS right now my database server listens on a specific port and accepts strings as queries. And for client I just telnet to my database server and can type queries in the telnet window.

    what needs to be done and better how it is to be doneYou already said the first part - you need to implement the interfaces.
    The second can only be answered by you in detail because it requires interacting with your existing code (your database.) No one here can tell you that because we don't know what you did. You would use TCP (Sockets) from the minimum you posted.
    You can look at the following.
    [http://java.sun.com/javase/6/docs/technotes/guides/jdbc/]
    The following is the real specification.
    [http://java.sun.com/products/jdbc/download.html]
    Keep in mind that you don't need to actually write code for most of the interface stuff - if you can't figure it out then have it throw a not implemented exception.

  • Partial SSL implementation for iplanet web server

    Hi,
    I would like to make a web server SSL enabled partially.
    Say something like this
    https://mysite:8080/htmlfiles/log.html
    Only the above url should be SSL protected.
    Other urls like http://mysite:8080/entryservlet shouldnt be SSL enabled
    Thanks in advance
    Regards
    Thameem

    iWS4.x:
    Create two instances - one on Port 80 and runs without SSL, and one on Port 443 that uses SSL. Configure your docs roots such that htmlfiles/log.html is not part of the doc-root for the insecure instance.
    iWS/S1WS6.x:
    Create a single instance with two listen sockets and two virtual servers. Otherwise the same as above.

  • Can I install a 30gb+ drive in a 1G?

    Posted this question here a while ago, gonna try again:
    Hi, I've got a 20gb 3G, I'm at the point where I need to upgrade to a bigger mp3 player, and I'm really interested in a 1G (rather than a newer iPod model) for a number of reasons. However, obviously I need something substantially BIGGER than 20gb to make my time worthwhile, and 1G only went up to 10.
    So... are 1Gs compatible with 3, 4, or 5G drives? Could I buy a larger (maybe 40gb or 60gb) drive and install it in an old first-gen model, or has the actual modelling of the drive/mobo changed since then so that it wouldn't fit? Really looking for an answer here, as if anyone can tell me that it works, I'll be buying a used 1G.
    Of course, since the newer drives are so much smaller, I realize that I'll have to put extra padding and whatnot in the 1G, but that's not a problem; I'm just worried about compatibility.
    Thanks for any help!

    Sure:
    ATA is the standard for most hard drives. the ipods use a type called ATA-5.
    "Advanced Technology Attachment. A disk drive implementation that integrates the controller on the disk drive itself. There are several versions of ATA, all developed by the Small Form Factor (SFF) Committee:
    ATA : Also known as IDE (Integrated, or Intelligent, Drive Electronics) supports one or two hard drives, a 16-bit interface and PIO modes 0, 1 and 2.
    ATA-2 : Supports faster PIO modes (3 and 4) and multiword (DMA modes (1 and 2). Also supports logical block addressing (LBA) and block transfers. ATA-2 is marketed as Fast ATA and Enhanced IDE (EIDE).
    ATA-3 : Minor revision to ATA-2.
    Ultra-ATA : Also called Ultra-DMA, ATA-33, and DMA-33, supports multiword DMA mode 3 running at 33 MBps.
    ATA/66 : A version of ATA proposed by Quantum Corporation, and supported by Intel, that doubles ATA’s throughput to 66 MBps.
    ATA/100 : An updated version of ATA/66 that increases data transfer rates to 100 MBps.
    ATA is also called Parallel ATA."
    -From http://www.x-emi.com/tech_terms.html
    Anyway, you can just buy any ATA-5 drive (Or get it from like another iPod) & then install it into yours.
    Look here for some ideas: http://www.newegg.com/Product/ProductList.asp?Submit=ENE&N=201015001470000314&Subcategory=14&description=&srchInDesc=&minPrice=&maxPrice=&ATTR1=&ATTR 2=&ATTR3=&ATTR4=&ATTR5=&ATTR6=&ATTR7=201015001470000314
    You can also install any CompactFlash Card, or CompactFlash MicroDrivein a 1st gen.

  • JDBC Thin vs Thick Driver

    Hello,
    We are looking for differences between Oracle JDBC Thin and OCI (thick) driver with respect to
    1. Peformance of the Java application.
    2. Maintenance and administration
    3. Known issues with OCI (thick) driver which is handled by Thin or vice versa.
    4. Better security
    Appreciate any help on the above.
    Thanks and Regards,
    Vamsi Mohan Harish

    1. Performance of the Java application.
    The difference in driver implementation is likely to be trivial compared to other considerations (network round trip time, application design, etc). However if you are really interested then chapter 19 of 'Java Programming with Oracle JDBC' by Donald Bales (O'Reilly) has some good information on this topic. It also happens to be available online: http://www.onjava.com/pub/a/onjava/excerpt/oraclejdbc_19/index.html
    Keep in mind that it is a little out of date now - you should run tests using the current versions of the drivers.
    2. Maintenance and administration
    The JDBC Thin driver is typically easier to update/distribute, as installation consists of copying a .jar file or two. The only case where OCI has an advantage is in the use of Oracle's naming layer for database service abstraction. Of course this assumes the database server is listening for TCP/IP and not the legacy protocols that are only supported by OCI. Failover configurations using TAF are supported by OCI only. The newer 'Fast Connection Failover' feature of 10g RAC can also run over Thin though.
    3. Known issues with OCI (thick) driver which is handled by Thin or vice versa.
    In my experience each has a roughly equal number of bugs. I find it easier to track them down in the Thin driver though :-)
    4. Better security
    The security options for the Thin driver are more limited with regard to external authentication and support for some of the Oracle Advanced Security features. However, both support the basics like encrypted connections. Chapter 23 of the JDBC driver docs goes into more depth: http://download-west.oracle.com/docs/cd/B14117_01/java.101/b10979/toc.htm
    Hope this helps.
    Jonathan.

  • Is the "Device Class Definition for Physical Interface Devices" specification implemented in Windows?

    Can I assume that Windows will be able to handle my physical interface device if I follow the "Device Class Definition for Physical Interface Devices" specification while writing the firmware?
    I'm trying to develop a device which handles rumble output from applications such as games. Applications would include e.g. racing games or simulators. I'm hesitant to just clone Xbox 360 Gamepad or Sidewinder USB reports. I'd like to correctly declare my
    device as something on its own while still making use of already implemented OS-specific drivers. The purpose of the mentioned specification is exactly that as far as I can tell. I wasn't able to find concrete information about its level of support though.
    The "USB device class drivers included in Windows" page (sorry I'm not allowed to post links yet..) seems to link to WinUSB which I'm not sure what to do with.

    Thanks for your response. Well if everything was implemented at that time and it's still available it should be fine since the specification document's last version is dated 1999. I was just hoping there would be any form of documentation whether it's
    supported and by which degree so I don't go through the trouble of figuring out how the firmware should be written according to the specification just to find out there is no OS driver implementation for it which would render my work more or less useless.
    So I suppose I'm forced to go the trial and error path?

  • Using Weblogic JDBC driver 5.1.0sp8  with MSSQL, throwing "abstract method" error when trying to use scrollable resultsets

    I am using the weblogic driver with Allaire JRun.
    Using these lines, I am trying to make my resultsets scrollable and updatable.
    dbConnection.createStatement( ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE
    ResultSet rs = queryStatement.executeQuery(query);
    When I run the code, I get this error ..
    java.lang.AbstractMethodError
    at allaire.jrun.sql.ConnectionProxy.createStatement(../sql/ConnectionProxy.java:413)
    at com.mindseye.utils.database.DBAccessor.executeQuery(DBAccessor.java:35)
    at com.fao.shopping.tag.HandleShoppingCartTag.checkExists(HandleShoppingCartTag.java:635)
    at com.fao.shopping.tag.HandleShoppingCartTag.doStartTag(HandleShoppingCartTag.java:90)
    at jrun__jsp__shoppingbag2ejsp14._jspService(jrun__jsp__shoppingbag2ejsp14.java:45)
    at allaire.jrun.jsp.HttpJSPServlet.service(../jsp/HttpJSPServlet.java:39)
    at allaire.jrun.jsp.JSPServlet.service(../jsp/JSPServlet.java:228)
    Everything works fine when I do not try and specify attributes to the statement
    object. (i.e. dbConnection.createStatement();)
    Anybody know what is going on?
    thanks,
    randy

    Hi. I don't see our code anywhere in the stacktrace, but I'll assume
    it's there somewhere. The basic fact is that our MS SQLServer driver
    implements practically zero of the JDBC 2.0 methods. There is a way
    to connect to this driver that has the methods defined, but then all
    the difference will be that you'll get an exception saying 'this jdbc 2.0
    method not implemented'.
    Joe
    randy shepherd wrote:
    >
    I am using the weblogic driver with Allaire JRun.
    Using these lines, I am trying to make my resultsets scrollable and updatable.
    dbConnection.createStatement( ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE
    ResultSet rs = queryStatement.executeQuery(query);
    When I run the code, I get this error ..
    java.lang.AbstractMethodError
    at allaire.jrun.sql.ConnectionProxy.createStatement(../sql/ConnectionProxy.java:413)
    at com.mindseye.utils.database.DBAccessor.executeQuery(DBAccessor.java:35)
    at com.fao.shopping.tag.HandleShoppingCartTag.checkExists(HandleShoppingCartTag.java:635)
    at com.fao.shopping.tag.HandleShoppingCartTag.doStartTag(HandleShoppingCartTag.java:90)
    at jrun__jsp__shoppingbag2ejsp14._jspService(jrun__jsp__shoppingbag2ejsp14.java:45)
    at allaire.jrun.jsp.HttpJSPServlet.service(../jsp/HttpJSPServlet.java:39)
    at allaire.jrun.jsp.JSPServlet.service(../jsp/JSPServlet.java:228)
    Everything works fine when I do not try and specify attributes to the statement
    object. (i.e. dbConnection.createStatement();)
    Anybody know what is going on?
    thanks,
    randy

  • Anybody use jtds driver with creator?

    Hello,
    I have a creator app that talks to our SQLServer via the jtds driver.
    I cannot update any records, I get a "result set is read only" message.
    I tried changing the concurrency to CONCUR_UPDATABLE and TYPE_SCROLL_SENSITIVE.
    Is there a better Driver to use?
    Thanks
    Frank

    I'm not completely sure I understand what you are saying, especially the part with the updateable and read-only tables (ResultSets are updateable/read-only, not tables). Could you provide an example (Java code or at least the SQL) illustrating your point?
    The problem with "this driver" is that in its last public release (1.0.2) it did not implement client side cursors (in fact it did, but only for Sybase). This support has now been extended to SQL Server in cases when the server isn't able to create a server side cursor, so jTDS will cache the whole result on the client and create a client side one. This behavior will be available in the next release (or you can get it from the CVS tree before that).
    The problem with transparently creating client side cursors is that this introduces a huge (memory and performance) overhead of which the user is unaware. This may lead to OutOfMemoryErrors simply because the table didn't have a primary key or the SELECT didn't include it.
    And now that we're here, let me point out that the DataDirect driver is not the most efficient, by far. There's even a test in their performance test suite (which they use only to point out that their driver is and will be the only one that doesn't fail that particular test), which creates a forward only ResultSet and then calls last() and beforeFirst() on it. This test only works because they cache the entire ResultSet, which may seem like a good thing, but it's totally unnecessary and if you compare the time it takes for that test to run with the time to do a simple next() through the exact same ResultSet it's orders of magnitude larger.
    And one final thing: the JDBC spec rightfully states that a JDBC driver implementation does not have to implement features that the underlying DBMS does not support. Creating a scrollable and/or updateable ResultSet from God knows what falls under this category in my oppinion. The SQL Server spec clearly states what conditions must be met by a SELECT query for a server side cursor to be created on it. You can't reasonably expect not to meet those conditions and still get what you want.
    Alin,
    The jTDS Project.

  • Help file for the Plug and Play driver of Agilent Technologies E5071C

    I just download the Plug and Play driver of Agilent Technologies E5071C from the below link:
    http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=5692
    I find that there is only some examples and not any help file with detail description for each input of those VIs. Although there is brief description for each VI when I press "Ctrl+H" on the VI,I still can't figure out how to use this driver. :-(
    Is there any help files with more detail description?
    Or any related examples for my reference? I hope to measure the S11 and S21 of the SMA cables

    The driver implements the commands defined by agilent.
    So look in the agilent programmers manual to find the meaning and how to handle the instrument.
    greetings from the Netherlands

  • Driver not found - JDBC - HELP PLZ!

    Hello everyone.
    i am trying to access my database and this is the code i made:
    public static void connectToDataBase()
    Connection connect = null;
    try{
    String driverName = "oracle.jdbc.driver.OracleDriver";
    String serverName = "192.168.5.6";
    String portNumber = "1521";
    String sid = "deve";
    String url = "jdbc:oracle:thin:@" + serverName + ":" + portNumber +
    ":" + sid;
    String usr = "emma";
    String pwd = "emma";
    //Load the JDBC driver
    Class.forName(driverName);
    //Connect to the base
    connect = DriverManager.getConnection(url,usr,pwd);
    catch(ClassNotFoundException e){
    System.out.println("Error---No database driver");
    catch(SQLException s){
    System.out.println("Error---No connection to the database");
    However, when i execute this program, a ClassNotFoundException is launched because i get the message "Error---No database driver".
    Can anyone help me please??
    thank you

    However, when i execute this program, a
    ClassNotFoundException is launched because i get the
    message "Error---No database driver".As mentioned already, you need to add the driver jar in the classpath. Depending on the type of application you are creating, the method for doing that would vary.
    For a simple standalone application, it can be achieved by simply including the JAR name (with path) in the classpath. This can be done by editing the CLASSPATH variable, which I mostly do not prefer, or using the command line switch -cp to set the classpath for the specific command.
    If you are dealing with web applications, you need not play around with the environment variables simply because it would not have any effect. Almost all application servers AFAIK ignore the environment settings. The best way of doing it is copying the driver jar to the WEB-INF/lib sub-directory under your webapp directory. (You could ignore this advice ATM if you haven't started with web applications yet). However, the preferred method of connection in case of webapps (or J2EE applications I might generalize) is using a datasource.
    Finally, a word of advice which I am often tempted to mention early on. Ensure that you are closing all the connections, statements and resultsets in your application once their job is done. Not doing so may lead to further complications in the future, depending on the driver implementations. The safest way is to call the close methods on all the JDBC resources in the finally block of your code to ensure that you always close the resources.
    Gluck!

  • Problems upgrading to JDBC 5.1 driver for MS SQL Server

    Hi,
    I recently upgraded to the Weblogic JDBC 5.1 driver for MS SQL Server and I am
    now receiving exceptions in my application when attempting to execute a prepared
    statement. I was previously using the Weblogic JDBC 4.x driver for MS SQL Server
    and everything was working fine without any problems. For some reason I am receiving
    a java.lang.CloneNotSupportedException using the new driver. I am using the setLong(),
    setString(), and setObject() methods of the PreparedStatement and then attempting
    to execute. The application code has not changed, so it seems that something
    has changed in the new driver implementation. Has anyone else had this problem
    or know a work around? Here is a snippet of the actual exception:
    S2 [09/30/02 10:46]: java.sql.SQLException: java.lang.CloneNotSupportedException
    : Error in TdsParameter clone: cannot make duplicate of Stream object
    S2 [09/30/02 10:46]: at weblogic.jdbcbase.mssqlserver4.TdsPreparedInputStream
    .<init>(TdsPreparedInputStream.java:99)
    S2 [09/30/02 10:46]: at weblogic.jdbcbase.mssqlserver4.TdsStatement.doEscapeP
    rocessing(TdsStatement.java:1317)
    S2 [09/30/02 10:46]: at weblogic.jdbcbase.mssqlserver4.TdsStatement.execute(T
    dsStatement.java:173)
    S2 [09/30/02 10:46]: at weblogic.jdbcbase.mssqlserver4.TdsStatement.executeUp
    date(TdsStatement.java:94)
    S2 [09/30/02 10:46]: at weblogic.jdbcbase.mssqlserver4.TdsStatement.executeUp
    date(TdsStatement.java:1438)
    Thanks, Nadeem.

    Nadeem Khokhar wrote:
    Is it true that the Weblogic jDriver for MS SQL Server is deprecated? That's the
    message that I got from BEA Support and here is the link they sent:
    http://edocs.bea.com/wls/docs70/mssqlserver4/install_jmsq4.html#415356
    It recommends using Microsoft's JDBC driver instead. Any thoughts on this? From
    what I understand and what I have read on the newsgroups, the Microsoft JDBC driver
    is still quite buggy and has numerous problems.
    Thanks, Nadeem.It is deprecated, but still supported, and is more recent in the download than the one in
    the 5.1 server. We do recommend MS's driver, or that of www.inetsoftware.de. The
    MS driver is fairly stable now, and may certainly have bugs, as does our driver. The MS
    driver is good because it is not deprecated, and supports JDBC 2.0 etc.
    Joe
    >
    >
    Joseph Weinstein <[email protected]> wrote:
    What version of 5.1? You should be running with the latest service pack.
    If that doesn't help, please download the latest 5.1 driver from our
    site, and
    make sure it's in the weblogic.classpath ahead of all other stuff, by
    editting the
    startWeblogic script.
    Joe
    Nadeem Khokhar wrote:
    Hi,
    I recently upgraded to the Weblogic JDBC 5.1 driver for MS SQL Serverand I am
    now receiving exceptions in my application when attempting to executea prepared
    statement. I was previously using the Weblogic JDBC 4.x driver forMS SQL Server
    and everything was working fine without any problems. For some reasonI am receiving
    a java.lang.CloneNotSupportedException using the new driver. I amusing the setLong(),
    setString(), and setObject() methods of the PreparedStatement and thenattempting
    to execute. The application code has not changed, so it seems thatsomething
    has changed in the new driver implementation. Has anyone else hadthis problem
    or know a work around? Here is a snippet of the actual exception:
    S2 [09/30/02 10:46]: java.sql.SQLException: java.lang.CloneNotSupportedException
    : Error in TdsParameter clone: cannot make duplicate of Stream object
    S2 [09/30/02 10:46]: at weblogic.jdbcbase.mssqlserver4.TdsPreparedInputStream
    <init>(TdsPreparedInputStream.java:99)
    S2 [09/30/02 10:46]: at weblogic.jdbcbase.mssqlserver4.TdsStatement.doEscapeP
    rocessing(TdsStatement.java:1317)
    S2 [09/30/02 10:46]: at weblogic.jdbcbase.mssqlserver4.TdsStatement.execute(T
    dsStatement.java:173)
    S2 [09/30/02 10:46]: at weblogic.jdbcbase.mssqlserver4.TdsStatement.executeUp
    date(TdsStatement.java:94)
    S2 [09/30/02 10:46]: at weblogic.jdbcbase.mssqlserver4.TdsStatement.executeUp
    date(TdsStatement.java:1438)
    Thanks, Nadeem.

Maybe you are looking for