Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

applet doesnt work on IE only

2 posts in JDBC Connect (product renamed to JConnect) Last posting was on 1997-10-07 00:59:32.0Z
Vanessa L. Sikkema Posted on 1997-10-03 13:01:53.0Z
Message-ID: <3434ECC1.F1A4539C@bsr.com>
Date: Fri, 03 Oct 1997 09:01:53 -0400
From: "Vanessa L. Sikkema" <sikkema@bsr.com>
Reply-To: sikkema@bsr.com
Organization: BSR
X-Mailer: Mozilla 4.01 [en] (WinNT; I)
MIME-Version: 1.0
Subject: applet doesnt work on IE only
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 24
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:195
Article PK: 251950

Recently I posted a question about a NoClassDefFoundError error and many
suggestions told me that I had to have the jdbc classes in my codebase.
Well I did. Evidently what did get working was to stop using a JAR
target, and just use the regular files from the Release version of the
applet. So I guess my first concern is: Why can't we use JAR's with
jdbc applets? Perhaps it is because the jdbc files have to be copied
over manually and thus are not in the JAR codebase? Will this get fixed
do you think?

More importantly my question is - Ok, now that I have the applet working
on Netscape and it successfully accesses and updates the database, how
come opening it in Internet Explorer gets me a No Suitable Driver
error? It does at least start the applet but the error occurs when
trying to access the database and an SQLException is caught. Now what
do I do?

-Vanessa L. Sikkema
-Business Systems Resources, Inc.


David Clegg Posted on 1997-10-07 00:59:32.0Z
Message-ID: <34398974.31C64586@sybase.com>
Date: Mon, 06 Oct 1997 17:59:32 -0700
From: David Clegg <davec@sybase.com>
X-Mailer: Mozilla 3.01 (X11; I; Linux 1.2.13 i586)
MIME-Version: 1.0
To: sikkema@bsr.com
Subject: Re: applet doesnt work on IE only
References: <3434ECC1.F1A4539C@bsr.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 39
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:185
Article PK: 251936


Vanessa L. Sikkema wrote:
>
> Recently I posted a question about a NoClassDefFoundError error and many
> suggestions told me that I had to have the jdbc classes in my codebase.
> Well I did. Evidently what did get working was to stop using a JAR
> target, and just use the regular files from the Release version of the
> applet. So I guess my first concern is: Why can't we use JAR's with
> jdbc applets? Perhaps it is because the jdbc files have to be copied
> over manually and thus are not in the JAR codebase? Will this get fixed
> do you think?

I've been successful using JAR files with Netscape - also, if Netscape
cannot resolve a class from the Jarfile, it should attempt to just
get the class from the web server (as if you never had an archive
tag). Don't know what to suggest.


>
> More importantly my question is - Ok, now that I have the applet working
> on Netscape and it successfully accesses and updates the database, how
> come opening it in Internet Explorer gets me a No Suitable Driver
> error? It does at least start the applet but the error occurs when
> trying to access the database and an SQLException is caught. Now what
> do I do?
IE still has that bug where static class initializers cannot be used
to register drivers with the registerDriver method on DriverManager.
Try:
DriverManager.registerDriver((Driver)(Class.forName(
"com.sybase.jdbc.SybDriver").newInstance());
before connecting.

>
> -Vanessa L. Sikkema
> -Business Systems Resources, Inc.