Thank you for this explanation. However, the JDBC-ODBC bridge really seems
to have major problems in JDK 1.2.2 (and the corresponding JDBC release). I
have experienced this myself and heard this from many other people using the
same version. I believe that it might have worked up to JDK 1.2.1, but as we
would like to go with the newer JDK for other reasons, the bridge
unfortunately is not an option for accessing SQL Server at this point.
-Mirko
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 14, 1999 3:35 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: ODBC and JSP
>
>
>
>
>
> Hi everyone on this thread,
>
> I have been listening, but too busy to respond immediately.
> Some of your comments made me think I should take some
> time to sound off a little.
>
> I have used the JDBC-ODBC bridge to access SQL Server
> and it works FINE. The major reason to utilize one of the third-
> party JDBC Drivers for SQL Server is more related to the JDBC
> Driver Model and the Type of Driver you may need ( even though
> SUN plays down it's use as more of a 'last resort', it is fully
> functional for some uses, and may be all you need to develop
> and support a product ).
>
> There are basically four different Types or Styles of JDBC Driver.
>
> If I am in an environment where there is native ODBC (such as in
> Windows 9x or NT) and I have the appropriate licensed ODBC
> Driver for my Database, and ODBC is working fine, then the JDBC-
> ODBC Bridge driver is potentially an appropriate choice, given
> certain factors, such as if everything will remain in this environment.
>
> The other Driver models reflect the varying needs of deployment
> and licensing, cost factors, lack of appropriate Drivers for a given
> platform, scalability of connection resources, etc.
>
> Other considerations might include the nature of the applications
> SQL standards compliance ( such as the need to remain RDBMS
> neutral), and datatype support, and cursor style support, etc.
>
>
> As an example:
>
> Project "BigWidget" will be sold to commercial clients who will
> be accessing the Java Beans via a Web Browser thin client
> solution ( ASP or JSP ). I choose to use Servlets (poss. EJB)
> as the deployment framework for my DB aware Beans.
>
> My next consideration is the RDBMS of choice, transaction volume,
> isolation support, deployment hardware, DBA skills, etc.
>
> It turns out that the vast majority of my market are skilled in and
> utilize Microsoft SQL Server ( not casting any judgements about
> my clients now, are you? ). So they dictate that I deliver my solution
> to be compatible with MS SS, and I now have to determine a few
> factors related to JDBC Driver.
>
> If the middleware where my Beans are deployed supports ODBC,
> and have a low transactional volume, and only need 'foward only',
> non-updateable cursor support, I may choose to package my
> Beans with a default use of the JDBC-ODBC Bridge Driver, and
> suggest that if their needs grow, they could then upgrade to support
> for a more robust Driver. I can write my code to configure itself for
> any Driver the client supplies, even expanding the cursor model
> if the driver supports it ( dynamic Driver loading and querying the
> MetaData for feature checking ).
>
> If my middleware server does not support ODBC natively, I have
> a few decisions to make about where the Beans will live, which
> JDBC Driver and Style to use. This choice will possibly impact
> scalability of the solution as well.
>
> Hope this helps to open a lively discussion around the proper
> architecture to support various needs and deployment issues.
>
> Arthur Alexander
> Senior Consultant,
> Computer Science Corporation
>
>
> -----Original Message-----
> From: Mirko Froehlich <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> Date: Tuesday, December 14, 1999 6:07 PM
> Subject: Re: ODBC and JSP
>
>
> >I might be getting off-topic here, but do you have any
> recommendations for
> >alternatives to access MS-Access databases via JDBC? I think
> that I am going
> >to use i-net Software's JDBC driver for SQL Server, but I might
> still need a
> >driver for MS-Access (or ODBC in general) if the JDBC-ODBC
> bridge does not
> >work out.
> >
> >-Mirko
> >
> >
> >> -----Original Message-----
> >> From: A mailing list about Java Server Pages specification and
> reference
> >> [mailto:[EMAIL PROTECTED]]On Behalf Of brian
> >> Sent: Tuesday, December 14, 1999 1:49 PM
> >> To: [EMAIL PROTECTED]
> >> Subject: Re: ODBC and JSP
> >>
> >>
> >> the jdbc-odbc bridge should be avoided, especially from servlets
> >> (and therefore
> >> jsp), as it is not threadsafe.
> >> -bml
> >>
> >> Mirko Froehlich wrote:
> >>
> >> > I am just fighting with a similar issue, although not (yet)
> >> from JSP, but
> >> > from a Java application. You cannot directly access ODBC data
> >> sources from
> >> > Java, but there are a couple of options that all involve JDBC.
> >> One of them
> >> > is the JDBC-ODBC bridge, which allows you to access ODBC data
> >> sources via
> >> > JDBC. Unfortunately, this is (according to Sun) experimental,
> >> and in fact
> >> > JDK 1.2.2 has some major problems. I was unable to get this
> >> working with SQL
> >> > Server, although I was able to successfully access an MS Access
> >> database via
> >> > JDBC-ODBC. There are some third-party drivers, for example a
> native JDBC
> >> > driver for SQL Server (from http://www.inetsoftware.de/),
> which seems to
> >> > work fine. I believe there are also third-party JDBC-ODBC
> >> bridges that might
> >> > be more robust. Sun has a nice list of JDBC drivers at this URL:
> >> > http://java.sun.com/products/jdbc/drivers.html
> >> >
> >> > -Mirko
> >> >
> >> > > -----Original Message-----
> >> > > From: A mailing list about Java Server Pages specification
> >> and reference
> >> > > [mailto:[EMAIL PROTECTED]]On Behalf Of Jeff Brown
> >> > > Sent: Tuesday, December 14, 1999 11:30 AM
> >> > > To: [EMAIL PROTECTED]
> >> > > Subject: ODBC and JSP
> >> > >
> >> > >
> >> > > Let me start by saying that I'm new to the whole JSP game. I'm an
> >> > > ActiveServerPage developer that needs to port all of my ASP's
> >> to JSP's for
> >> > > the next release of a product I'm working on.
> >> > >
> >> > > What I need to do is open a connection to an ODBC source (in this
> >> > > case a SQL
> >> > > 7.0 Database) and run simple SQL calls against it. The code I
> >> > > would use in
> >> > > an ASP is:
> >> > >
> >> > > Set Conn = Server.CreateObject("ADODB.Connection")
> >> > > Conn.Open "dsn=SQLCharDB;uid=sa;pwd="
> >> > >
> >> > > First of all, I need to figure out how to set up an ODBC
> >> connection to my
> >> > > SQL DB on a Solaris 7 box. Then I need to learn the correct
> >> syntax for
> >> > > opening a connection to said ODBC from inside my JSP's.
> >> Currently the web
> >> > > server I'm using is Netscape Enterprise 4.0, but I'll
> >> eventually be using
> >> > > Apache as well.
> >> > >
> >> > > Any information would be greatly appreciated.
> >> > >
> >> > >
> >> > > Jeffrey W. Brown
> >> > > Test Engineer
> >> > > Citr!x Systems, Inc.
> >> > > PHONE: (954) 267-2846
> >> > > EMAIL: jeff.brown @ citrix.com
> >> > >
> >>
> >> Brian M. Long
> >> RandomWalk Computing, Inc.
> >> [EMAIL PROTECTED]
> >> 212.480.5280 x276
> >>
>
>
>
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
