Questions on JConnect 2.2
== I'm going to include a rather grumpy message one of my developers sent
== to Sybase Tech Support regarding his evaluation of the trial copy of
== JConnect 2.2 he recently downloaded. I confess I know nothing about
== Java, but I'm interested to see what comments I can get from this
== group. I suspect, from the tone of this message, that we may not be
== getting any response from Tech Support...
Instead of sending this message to Sybase your "developer" should have
read the documentation (and the FAQ in particular) more carefully. S/he
missed several key points. Also, note that jConnect 3.0 is already
available.
== A) JDK1.1 is not currently supported by any web browsers
How about Netscape 4.0.X and IE 4.0...
== so we have to use JDK1.02
... go figure
== B) JDK 1.02 security will only allow the core java packages to be
== transmitted over the web.
This should probably read "will not allow any". The client host must
have a complete JDK installation.
== C) The JDBC packages are not core java packages so java.sql classes cannot
== be transmitted over the web.
This is correct, for a change.
== D) The Sybase packages are not core packages so sybase.java.sql classes
== cannot be transmitted over the web.
???
== F) Sybase is aware of this and in their FAQ they recommend changing the
== name of the sybase/java directory to sybase/jdbc and re-compiling.
Where did you read this?
Take a look at
http://www.sybase.com/products/internet/jconnect/jdbcfaqs3.html#q5
which explains in detail which zip files you need for development
(syb102.zip for JDK102, sybjdbc.zip for JDK11) and which packages you
need to import (e.g. jdbc.sql.* for JDK102, java.sql.* for JDK11).
Your developer should also take a look at
http://www.watcom.com/devnotes/java/jdbc_and_applets.html
jConnect specific news group are at
== G) The recomended method does NOT work because the sybase.java.sql classes
== KNOW they are sybase.java.sql classes and NOT sybase.jdbc.sql classes.
There are no sybase.java.sql classes nor sybase.jdbc.sql. The jConnect
distribution contain jdbc.sql (which is a java.sql substitute) and com.sybase.jdbc.
== H) You can fool the sybase.java.sql classes into believing they are
== sybase.jdbc.sql classes if you modify the source code.
== I) After you modify the source code and re-compile the sybase.jdbc.sql
== package can be transmitted over the web.
== J) The sybase.jdbc.sql.Connection class needs the java.util.Properties
== class in order to connect to the database.
== K) The java.util package is NOT a core java package so the
== java.utils.Properties class cannot be transmitted over the net.
== L) The source code for the java.utils package is not available - so you
== cannot fool the java.util.Properties class into thinking it is part of
== some other package.
Get a complete JDK installation. java.util.Properties is in classes.zip
of the JDK 1.0.2 download from Sun. Period.
== This all leads me to the following conclusion: The trial
== version of JConnect 2.2 for JDK 1.02 is absolutely useless
== for our purposes. And while the full version may work fine
== I am now suspicious. If Sybase is this slack about the
== trial versions they make available what kind of support can
== we expect if we buy the damned thing, and what is our level
== of confidence that Sybase has the slightest idea what they
== are doing?
No comment on who has or has not the slightest idea.
regards
Martin
BEA Systems, JOLT Development
