From: Ward Mullins Subject: Re: 100% Java JDBC driver for Oracle? Date: 1997/03/27 Message-ID: <333B6DAD.A6F@thoughtinc.com>#1/1 References: <3334C999.4121@ostendorf.com> <5h6hbo$41p@news00.btx.dtag.de> <33396A50.2242@worldnet.att.net> To: netac Organization: THOUGHT Inc. Reply-To: ward@thoughtinc.com Newsgroups: comp.databases.oracle.tools,comp.lang.java.tech netac wrote: > > Torsten Greiff wrote: > > > > Hello Karl, > > > > There is a JDBC driver from Weblogic (T3). > > It is 100 % Java and it's not using ODBC. > > We are currently developing Java applets using this driver and it's fine. > > > > http://www.weblogic.com/ > > > > regards Tosten > > What does this "driver" provide? If I already have written a ProC > method 4 function for source code level integration, why can't I use > this under Java? Maybe because you can't deploy it in the browser? The whole point of products such as weblogic's t3, and our 3-tier database middleware product CocoBase, is to provide a browser capable system suitable for a 3-tier environment. Since applets running inside of browsers don't have access to local resources, they also don't have the ability to get to local dll's such as the one that you probably created. What you did is produced your own proprietary non-jdbc driver interface which means that if for some reason you wanted to write applications which went to sybase instead, would require you write another compatible sybase driver to preserve your application code investment. If you have the time and energy to write all of your own drivers, then you probably don't need weblogic. Most people find it much cheaper to buy those sorts of solutions rather than build them... Just my $.02 Ward Mullins THOUGHT Inc. ward@thoughtinc.com http://www.thoughtinc.com