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.

Problems with JConnect with MS Visual J++

3 posts in JDBC Connect (product renamed to JConnect) Last posting was on 1997-06-10 08:03:07.0Z
Dharani Ramamoorthy Posted on 1997-06-05 14:32:14.0Z
Message-ID: <3396CDEE.CBF9D1A7@sparc.isl.net>
Date: Thu, 05 Jun 1997 09:32:14 -0500
From: Dharani Ramamoorthy <dharani@sparc.isl.net>
X-Mailer: Mozilla 4.0b4 [en] (WinNT; I)
MIME-Version: 1.0
Subject: Problems with JConnect with MS Visual J++
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Newsgroups: sybase.public.jdbcconnect
Lines: 55
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:719
Article PK: 252470

I am running Window NT 4.0 and enabled my webserver which is part of NT
workstation. I have a default home page which shows up when any one in
our intranet trying to connect to my system. I added an entry in that
default html file to have a link to ISQL applet ( used the ISQL class
in the sample directory which is part of sybase JConnect ).
eg: <LI><A HREF=http://isemr:8000/sample/gateway.html>A java applet to
query SQL Server</A></LI>.
This link works fine( execute the applet and get results from the sql
server ) on my system or at any one else's system with in the intranet.

Now the real problem comes. I tried to use the source provided with
JConnect for the ISQL applet and compiled my own ISQL class in MS visual
J++. Replaced the ISQL class ( JConnect's one ) with my ISQL class(
compiled with MS Visual J++ ) in my NT web server. I could execute
successfully my version of ISQL applet on my workstation. But other
people with in the intranet when they try to execute the applet by
cliking on the link on my default html page, they get the following
error in the status window of the netscape browser "Applet can't start:
Class ISQL got a security violation: method verification error.".

I successfully compiled many applet classes in MS Visual J++ with out
JDBC calls and put it in my webserver. Those applets can be executed on
my workstation and any one else's workstation with in our intranet with
out any problem.

This problem is with MS Visual J++ and using JDBC calls implemented by
the JConnect. In that scenario only, I get the above error. Any ideas or
thoughts?. I believe the ISQL class which comes with JConnect may be
compiled with SUN compiler. I have not tried myself compiling the ISQL
source with any other compiler other than MS Visual J++.

My environment:

Development tool : MS Visual J++ 1.1
OS : Windows NT 4.0
JConnect ver : file size 1942KB dated 5/14/97
WebServer : NT Workstation web server
Browser : Netscape 3.01 Gold

Pleas let me know if you need any other information
Dharani Ramamoorthy
Ramamoorthy.Dharani@mayo.edu


Dharani Ramamoorthy Posted on 1997-06-09 19:33:54.0Z
Message-ID: <339C5AA2.FBAD642A@sparc.isl.net>
Date: Mon, 09 Jun 1997 14:33:54 -0500
From: Dharani Ramamoorthy <dharani@sparc.isl.net>
X-Mailer: Mozilla 4.0b4 [en] (WinNT; I)
MIME-Version: 1.0
Subject: Re: Problems with JConnect with MS Visual J++
X-Priority: 3 (Normal)
References: <3396CDEE.CBF9D1A7@sparc.isl.net>
Content-Type: text/plain; charset=iso-8859-1
Newsgroups: sybase.public.jdbcconnect
Lines: 26
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:711
Article PK: 252463

I have posted a few days back about the problem of running a applet (
compiled with MS Visual C++ ) which uses the JDBC APIs. I have tried
compiling my applet code with Cafe as well as Sun javac. Problem still
continued. That helped me to eliminate that it is not with the compiler.
After lot of trial and error, I have figured out the problem. My applet
was served to other users in the intranet using NT workstation webserver
and not using the Cascaded HTTPD server which comes along with JConnect
product. When I changed that scenario, i,e I changed my setup so that my
applet was served by the HTTPD server, other users in the intranet could
start running the applet.

That brings me another question. What is the difference between the
Sybase supplied HTTPD web server and the NT workstation Web server. Is
that any way, I can change the NT workstation Webserver to act as the
same way as HTTPD server does. How about the netscape webserver. Will it
work with JDBC enabled applets.


Joe Carter Posted on 1997-06-10 08:03:07.0Z
Message-ID: <339D0A3B.5D61E6C8@man.brite.co.uk>
Date: Tue, 10 Jun 1997 09:03:07 +0100
From: Joe Carter <joseph.carter@man.brite.co.uk>
Organization: Brite Voice Systems Ltd
X-Mailer: Mozilla 3.01 (X11; I; Linux 2.0.29 i586)
MIME-Version: 1.0
Subject: Re: Problems with JConnect with MS Visual J++
References: <3396CDEE.CBF9D1A7@sparc.isl.net> <339C5AA2.FBAD642A@sparc.isl.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 28
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:708
Article PK: 252460


Dharani Ramamoorthy wrote:
>
8<
>
> That brings me another question. What is the difference between the
> Sybase supplied HTTPD web server and the NT workstation Web server. Is
> that any way, I can change the NT workstation Webserver to act as the
> same way as HTTPD server does. How about the netscape webserver. Will it
> work with JDBC enabled applets.

The Cascade server supports the http CONNECT protocol which
effectively allow to you talk to databases machine other than your web
server.
If you do not need to do this you can just use a normal web server.

If you do, you can use a normal web server to supply the applet, and
have the
cascasde server running as well, to support the relaying to the other
databases, reducing the load on the Cascade server.
e.g. the NT server on port 80 (as per normal) and run the Cascade
on port 8000.

AFAIK most web servers do not support the CONNECT protocol.
I'd be interested to hear about others that do!

--
Joe Carter Software Engineer
Brite Voice Systems Ltd, Gatley, Cheshire. UK.
mailto:joseph.carter@man.brite.co.uk