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.

jConnect and IE4

4 posts in JConnect version 3.0 Last posting was on 1998-10-05 15:05:29.0Z
Craig A. De Ruisseau Posted on 1998-10-05 11:55:50.0Z
Message-ID: <3618B3C6.8963A721@meganet.net>
Date: Mon, 05 Oct 1998 07:55:50 -0400
From: "Craig A. De Ruisseau" <cad@meganet.net>
Reply-To: cad@meganet.net
X-Mailer: Mozilla 4.5b2 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: jConnect and IE4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jconnect40,sybase.public.jconnect30
Lines: 25
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jconnect40:236 sybase.public.jconnect30:1705
Article PK: 256523

Hi, all:

I am at a client now where I am using jConnect 3.0 and Internet Explorer
4.0 to access an ASE database through a 1.1 Java applet. I am
developing with Windows NT and this is predominantly an NT/UNIX shop.
The applet works very well on the machines running on the Windows NT
platform but not very well on machines running Windows 95. As a matter
of fact, Internet Explorer usually crashes immediately when the page
with the applet is loaded. I have been informed by MIS here at the
client site that they have seen this problem in the past and when
hitting an applet that uses jConnect have had more success with Internet
Explorer 4 on Win95 when they converted the HTML page to use the Java
Plug-In . Does anyone know if there is a bug in jConnect 3.0 that
causes this crash on Windows 95 or might we being seeing something
else? If it is a bug in jConnect 3.0 is it fixed in any patches or in
jConnect 4.0?

Thanks,
Craig


David Wolf Posted on 1998-10-05 12:46:16.0Z
Message-ID: <3618BF98.640EB9CC@sybase.com>
Date: Mon, 05 Oct 1998 14:46:16 +0200
From: David Wolf <dwolf@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.06 [en] (WinNT; I)
MIME-Version: 1.0
Subject: Re: jConnect and IE4
References: <3618B3C6.8963A721@meganet.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jconnect40,sybase.public.jconnect30
Lines: 36
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jconnect40:235 sybase.public.jconnect30:1704
Article PK: 255141

There were some issues with how you loaded the driver thanks to IE's
stricter Security implementation, but these normally caused a
SecurityException, not a crash. You might try registering the driver as:

DriverManager.registerDriver((java.sql.Driver)
Class.forName("com.sybase.jdbc.SybDriver").newInstance());

Does this help?

Dave Wolf
Jaguar Product Team

Craig A. De Ruisseau wrote:

> Hi, all:
>
> I am at a client now where I am using jConnect 3.0 and Internet Explorer
> 4.0 to access an ASE database through a 1.1 Java applet. I am
> developing with Windows NT and this is predominantly an NT/UNIX shop.
> The applet works very well on the machines running on the Windows NT
> platform but not very well on machines running Windows 95. As a matter
> of fact, Internet Explorer usually crashes immediately when the page
> with the applet is loaded. I have been informed by MIS here at the
> client site that they have seen this problem in the past and when
> hitting an applet that uses jConnect have had more success with Internet
> Explorer 4 on Win95 when they converted the HTML page to use the Java
> Plug-In . Does anyone know if there is a bug in jConnect 3.0 that
> causes this crash on Windows 95 or might we being seeing something
> else? If it is a bug in jConnect 3.0 is it fixed in any patches or in
> jConnect 4.0?
>
> Thanks,
> Craig


Craig A. De Ruisseau Posted on 1998-10-05 14:02:22.0Z
Message-ID: <3618D16D.3C35E12F@meganet.net>
Date: Mon, 05 Oct 1998 10:02:22 -0400
From: "Craig A. De Ruisseau" <cad@meganet.net>
Reply-To: cad@meganet.net
X-Mailer: Mozilla 4.5b2 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: jConnect and IE4
References: <3618B3C6.8963A721@meganet.net> <3618BF98.640EB9CC@sybase.com>
Content-Type: multipart/alternative; boundary="------------389C2F7CE4059B11797393D3"
Newsgroups: sybase.public.jconnect40,sybase.public.jconnect30,powersoft.public.powerj.database
Lines: 173
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jconnect40:234 sybase.public.jconnect30:1703 powersoft.public.powerj.database:2718
Article PK: 256522

Thanks for the reply, Dave.  I am not sure whether it will help or not as the applet was made with PowerJ and all the driver registration etc. are done in the create method which, as you no doubt know, is read-only.  I could rewrite that portion of the applet in straight JDBC so that it is outside the PowerJ create method and doesn't use the PowerJ components but this would represent a fairly large task to have to do at this point in the application and as you said before - it's a SecurityException that we should see and not a crash.

So maybe an offshoot of my original question would be as follows.  Normally in PowerJ, using the connection and query objects the registration is done in read-only code like so:

        transaction_1.registerDriver( "com.sybase.jdbc.SybDriver" ); // this is the line to change
        transaction_1.setDriverName( "com.sybase.jdbc.SybDriver" );
        transaction_1.setName( "Form1.transaction_1" );
        transaction_1.setDataSource("jdbc:sybase:Tds:localhost:9977");
        transaction_1.setUserID("dba");
        transaction_1.setPassword("sql");

Is there a way to change the way a driver is actually registered in PowerJ when using the Powersoft components?  If your suggestion is the solution then this second question would be great to know the answer to.

Thanks a lot ,
Craig

David Wolf wrote:

There were some issues with how you loaded the driver thanks to IE's
stricter Security implementation, but these normally caused a
SecurityException, not a crash.  You might try registering the driver as:

DriverManager.registerDriver((java.sql.Driver)
        Class.forName("com.sybase.jdbc.SybDriver").newInstance());

Does this help?

Dave Wolf
Jaguar Product Team

Craig A. De Ruisseau wrote:

> Hi, all:
>
> I am at a client now where I am using jConnect 3.0 and Internet Explorer
> 4.0 to access an ASE database through a 1.1 Java applet.  I am
> developing with Windows NT and this is predominantly an NT/UNIX shop.
> The applet works very well on the machines running on the Windows NT
> platform but not very well on machines running Windows 95.  As a matter
> of fact, Internet Explorer usually crashes immediately when the page
> with the applet is loaded.  I have been informed by MIS here at the
> client site that they have seen this problem in the past and when
> hitting an applet that uses jConnect have had more success with Internet
> Explorer 4 on Win95 when they converted the HTML page to use the Java
> Plug-In .  Does anyone know if there is a bug in jConnect 3.0 that
> causes this crash on Windows 95 or might we being seeing something
> else?  If it is a bug in jConnect 3.0 is it fixed in any patches or in
> jConnect 4.0?
>
> Thanks,
> Craig


Eric Giguere Posted on 1998-10-05 15:05:29.0Z
From: "Eric Giguere" <giguere@sybase.com>
References: <3618B3C6.8963A721@meganet.net> <3618BF98.640EB9CC@sybase.com> <3618D16D.3C35E12F@meganet.net>
Subject: Re: jConnect and IE4
Date: Mon, 5 Oct 1998 10:05:29 -0500
Lines: 9
X-Newsreader: Microsoft Outlook Express 4.72.3115.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <YCHkRCG89GA.190@forums.powersoft.com>
Newsgroups: sybase.public.jconnect40,sybase.public.jconnect30,powersoft.public.powerj.database
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jconnect40:233 sybase.public.jconnect30:1702 powersoft.public.powerj.database:2717
Article PK: 256521

The Transaction.registerDriver() function calls newInstance to create a new
instance
of the driver and then registers it by calling DriverManager.registerDrive,
so changing
that call won't help you -- it's already doing the correct thing.

Eric