Running class files produced by Sun's jdk1.1.1 using Micrsoft's jview
Martin
For the past month, I have been using Sun's JDK1.1.1 to write some Java
code on Windows95 to access an Informix database residing on an IBM Unix
box (running AIX).
I use Sun's JDBC-ODBC bridge along with OpenLink's ODBC drivers which are
installed on Windows95.
The Java source code compiles and runs fine using Sun's java compiler and
virtual machine. I use 1.1 events. The Event model was significantly
changed from Sun's JDK 1.0 to 1.1.
When I try to compile Java source code that compiled fine with Sun's
JDK1.1.1, I find Microsoft Visual J++ 1.1 Trial Edition stops with compile
errors. The compiler errors seem to be in the event code.
The Microsoft Java Virtual Machine (jview located in c:\windows) seems to
only be able to partially run compiled classes output by Sun's compiler.
I thought that Microsoft's Visual J++ trial edition was supposed to support
Sun's JDK1.1. Or maybe I have got things wrong.
I did set my CLASSPATH to be something like:
SET CLASSPATH=C:\jdk1.1.1\lib\classes.zip;.;c:\java;
so that Microsoft's JVM can use Sun's classes needed for database
connectivity via the bridge.
Can something please help me with what is going wrong? I don't want to use
a primitive command-line only compiler, namely Sun's, for large scale
development projects. But I don't want to use Microsoft's J++ if their
product isn't truely cross-platform.
Does anyone know how good Symantec Cafe for Windows95 is? Does Symantec
Cafe support 1.1 events yet? I don't want to use a compiler, only to have
to hand modify all the event code from 1.0 to 1.1 later. Does Symantec Cafe
allow drag and drop construction of forms/GUI interfaces?
If you can response, can you also copy directly to me e-mail address given
below as I check newsgroups less often than e-mail.
Also I have the questions below:
1) Does Microsoft's Visual J++ 1.1 support the new event model introduced
in Sun's JDK 1.1?
2) Can you use Sun's classes that come with Sun JDK1.1.1 with Microsoft's
J++ compiler and virtual machine?
3) When will the Microsoft Visual J++ Profession Edition 1.1 be released?
4) I heard there were problems connecting to databases using Sun's
JDBC-ODBC bridge with J++ due to differences between C call support in JDK
and J++. Have these been fixed yet?
5) When I use Sun's JDK Java Virtual Machine (java from the command line) I
get a cheesy DOS box handing behind my Java app. To get around this I had
to write a C program that loads up Sun's Virtual Machine and then calls the
main method in the Java class, from the same C program, I want to start
from. How can I do the same thing with Microsoft's software.
Thanks,
Martin
e-mail address: mara...@compuserve.com
Martin Westermeier
On Fri, 16 May 1997 17:13:55 -0400, "Martin" <mara...@compuserve.com>
wrote:
>Also I have the questions below:
>
>1) Does Microsoft's Visual J++ 1.1 support the new event model introduced
>in Sun's JDK 1.1?
>2) Can you use Sun's classes that come with Sun JDK1.1.1 with Microsoft's
>J++ compiler and virtual machine?
>3) When will the Microsoft Visual J++ Profession Edition 1.1 be released?
>4) I heard there were problems connecting to databases using Sun's
>JDBC-ODBC bridge with J++ due to differences between C call support in JDK
>and J++. Have these been fixed yet?
>5) When I use Sun's JDK Java Virtual Machine (java from the command line) I
>get a cheesy DOS box handing behind my Java app. To get around this I had
>to write a C program that loads up Sun's Virtual Machine and then calls the
>main method in the Java class, from the same C program, I want to start
>from. How can I do the same thing with Microsoft's software.
>
>Thanks,
>
>Martin
>e-mail address: mara...@compuserve.com
I can only answer a few questions
1.) No
2.) Yes, I´ve tried it and I´vo got no problems
3.) It´s released, I´ve got this Version last week
4.) ?
5.) ?
Greetings
Martin
Tom Archer
I'll take a stab at the other two ;)
4. JDBC/ODBC is not supported with VJ 1.1. There has been some confusion
about this in this newsgroup. However, Microsoft themselves have said that
it is not supported. Microsoft is pushing their own database standards
(what a surprise!!!) : DAO and RDO. Additionaly, if you go to MS's web page
for VJ, there is an article on VJ 1.1 that also states that JDBC is not
supported. As a matter of fact, we had to pull our JDBC chapters because MS
has dumped support for it and write DAO and RDO chapters.
5. I never use java.exe, so I don't know this one for sure. However, can
you not specify your 'C' application in the Project Settings dialog? Since
I only use jview.exe when using a command line interpreter, so I can't test
this myself.
Cheers,
Tom Archer
tar...@mindspring.com
==================
co-author, "Visual C++ 5.0 Bible"
co-author, "Visual J++ 1.1 Bible"
Martin Westermeier wrote in article <3382e23d...@news.rhein-neckar.ne
tsurf.de>...
Stephen Mueller
Martin wrote:
> 5) When I use Sun's JDK Java Virtual Machine (java from the command line) I
> get a cheesy DOS box handing behind my Java app. To get around this I had
> to write a C program that loads up Sun's Virtual Machine and then calls the
> main method in the Java class, from the same C program, I want to start
> from. How can I do the same thing with Microsoft's software.
5) have you tried using java_g.exe instead of java.exe? I seem to
remember reading somewhere that it starts the VM without the console
"DOS box" window hanging around.
Regards,
Stephen Mueller
--
// Stephen Mueller -- Software/Systems Engineer ste...@rnsi.net \\
\\ Richards Network Solutions, Inc. http://www.rnsi.net //
// (Me.opinions != Employer.opinions) \\
Thornton Prime
In article <3382e23d...@news.rhein-neckar.netsurf.de>, mwes...@rhein-neckar.netsurf.de (Martin Westermeier) wrote:
>On Fri, 16 May 1997 17:13:55 -0400, "Martin" <mara...@compuserve.com>
>wrote:
>>in Sun's JDK 1.1?
No, but Microsoft's SDK for Java 2.0 Preview does. It works well with J++ and
IExplorer (but I haven't tried debugging yet).
>>2) Can you use Sun's classes that come with Sun JDK1.1.1 with Microsoft's
>>J++ compiler and virtual machine?
Yes, the MS SDK for Java 2.0 Preview includes these.
You will undoubtedly run into problems using the JDK 1.1.1 classes without
first using the MS SDK 2.0 Preview upgrade.
>>4) I heard there were problems connecting to databases using Sun's
>>JDBC-ODBC bridge with J++ due to differences between C call support in JDK
>>and J++. Have these been fixed yet?
It was never broken. J++ and JVIEW have been able to use JDBC since early JDBC
releases.
Microsoft's Java VM uses a different native code interface than the one used
by Sun, though, so native code JDBC drivers (like the JDBC-ODBC Bridge) did
not work. JDBC drivers written entirely in Java have worked since early on.
>>5) When I use Sun's JDK Java Virtual Machine (java from the command line) I
>>get a cheesy DOS box handing behind my Java app. To get around this I had
>>to write a C program that loads up Sun's Virtual Machine and then calls the
>>main method in the Java class, from the same C program, I want to start
>>from. How can I do the same thing with Microsoft's software.
Microsoft has a tool called WJVIEW which does what you already wrote code to
do. It is included in the MS SDK for Java.
..
>1.) No
>2.) Yes, I扉e tried it and I扉o got no problems
>3.) It愀 released, I扉e got this Version last week
>4.) ?
>5.) ?
Thornton Prime
I hate to sound like a Micro$oft spokesperson. I hate MS as much as the next
Java developer. I think we need to be honest, though, about what Microsoft has
and has not done with Java.
In article <eGf#WsiZ8...@uppssnewspub04.moswest.msn.net>, "Tom Archer"
<tar...@attinview.com> wrote:
>4. JDBC/ODBC is not supported with VJ 1.1. There has been some confusion
>about this in this newsgroup. However, Microsoft themselves have said that
>it is not supported. Microsoft is pushing their own database standards
>(what a surprise!!!) : DAO and RDO. Additionaly, if you go to MS's web page
>for VJ, there is an article on VJ 1.1 that also states that JDBC is not
>supported. As a matter of fact, we had to pull our JDBC chapters because MS
>has dumped support for it and write DAO and RDO chapters.
JDBC has worked with Microsoft's Java VM and with Visual J++ since early on.
What did not (and still do not work) are the JDBC DRIVERS THAT REQUIRE NATIVE
CODE. Microsoft does not use the same native code interface as used by Sun and
JavaSoft. Netscape uses another interface still.
JavaSoft has made their native code interface part of JDK 1.1. ALL JAVA
LICENCEES ARE CONTRACTUALLY BOUND TO IMPLEMENT IT. Microsoft is fighting this
part of their contract, saying that they were granted special terms. They say
the terms of their contract state they have rights to develop the reference
implementation Java VM for Win32. They believe that means they have
the right to decide what native code interface the JavaVm for Win32
will use. JavaSoft disagrees.
Anyway, JDBC WILL WORK as long as you use Type 3 and Type 4 JDBC drivers
(which are written entirely in Java).
Microsoft distributes JDBC with their SDK for Java 2.0 Preview. As far as I
know, MS has always said they would support the full Java API, including JDBC
(they argue that the native code interface falls outside of the Java API). In
fact, Microsoft has released a JDBC driver for ADO, a Type 1 driver which uses
the MS native code interface, much like the JDBC-ODBC bridge that JavaSoft
released with JDBC and JDK 1.1.
The MS SDK for Java 2.0 Preview is available at www.microsoft.com/java.
Thornton
Matthew D. Siple
Martin,
My understanding of J++ is that it is JDK1.01 compliant and implements
only the parts of JDK1.1 that Microsoft likes. Although they must
support the entire JDK1.1 according to their contract, they have
six months after the official release of JDK1.1.to do so.
This is the very reason that JavaSoft is implementing the PURE
JAVA branding. This type of icompatability across platforms will
kill Java. (My personal opinion is that this is the very reason
Microsoft is making it's version incompatible -- divide and conqure )
Of course I dont rememeber where I got this information and since
my wife is fond of tossing all my computer magazines more than
a month old in the recycle bin, I cant seem to find the actual article
I read that I got this from. In any case, you should be able to hit
the Microsoft home page and dig out the specs on what is officially
supported in J++ latest version.
- matt
Tom Archer
Hi Thornton,
I don't think you sound like a MS spokesperson at all. You're simply
relaying info that MS themselves should be making clearer. When our
Acquisitions Editor went to a trade show last week, MS told him that JDBC
was not supported in J++. Hence our conclusion to dump JDBC. I would still
recommend DAO to anyone that is using J++ from the simple fact that both
technologies belong to MS and, in my opinion, you won't see JDBC support
(such as it is) for very long.
Obviously, MS is not too concerned with supporting it. The reason I say
that is because:
1) they don't document it worth a damn
2) as mentioned above, their own techs can't help you
3) their web site talks exclusively about DAO/RDO in terms of db support
4) they published an article on their web site stating that JDBC is no
longer supported
5) the db wizards were created to support DAO and RDO (IOW, there is no
support for JDBC in their wizards)
Tom Archer
tar...@mindspring.com
==================
co-author, "Visual C++ 5.0 Bible"
co-author, "Visual J++ 1.1 Bible"
Thornton Prime wrote in article <5m07pn$6...@argentina.earthlink.net>...
Michael Gratton
Tom Archer wrote in article ...
>Hi Thornton,
>
>I don't think you sound like a MS spokesperson at all. You're simply
>relaying info that MS themselves should be making clearer. When our
>Acquisitions Editor went to a trade show last week, MS told him that JDBC
>was not supported in J++. Hence our conclusion to dump JDBC. I would
still
Wow what an obtuse connection to have made. Did you realize that JDBC and
OBDC have the same roots? Just because you cant drag-n-drop and object
onto the gui and "viola!" have a connection to an app... BIG DEAL! spend
a day coding and you have everything you need. DAO is SLOW, platform
specific, supports a pitifully few databases. Why are you using java? God
go use VB. Using java and then LOCKING youself into one platform makes
absolutely NO sense whatsoever.
JDBC is just a tool to do things, like odbc is. It is not a Javabean.
>recommend DAO to anyone that is using J++ from the simple fact that both
>technologies belong to MS and, in my opinion, you won't see JDBC support
>(such as it is) for very long.
HUH? Where exactly did you hear/read/see this?
>
>Obviously, MS is not too concerned with supporting it. The reason I say
>that is because:
>
>1) they don't document it worth a damn
>2) as mentioned above, their own techs can't help you
>3) their web site talks exclusively about DAO/RDO in terms of db support
>4) they published an article on their web site stating that JDBC is no
>longer supported
>5) the db wizards were created to support DAO and RDO (IOW, there is no
>support for JDBC in their wizards)
>
I think you obviously dont understand what JDBC is. Have you actually seen
ODBC documentation for C++ or VB or any other windows development platform.
Please, learn about what you are talking about before you spread this kind
of junk.
>Tom Archer
>tar...@mindspring.com
>==================
>co-author, "Visual C++ 5.0 Bible"
>co-author, "Visual J++ 1.1 Bible"
>
Wow, with these credentials i would have expected you to have known what
JDBC, ODBC and the like are all about.
> Thornton Prime wrote in article <5m07pn$6...@argentina.earthlink.net>...
>>I hate to sound like a Micro$oft spokesperson. I hate MS as much as the
>next
>>Java developer. I think we need to be honest, though, about what
Microsoft
>has
>>and has not done with Java.
>>
>>In article <eGf#WsiZ8...@uppssnewspub04.moswest.msn.net>, "Tom
Archer"
>><tar...@attinview.com> wrote:
>>>4. JDBC/ODBC is not supported with VJ 1.1. There has been some
confusion
>>>about this in this newsgroup. However, Microsoft themselves have said
>that
>>>it is not supported. Microsoft is pushing their own database standards
>>>(what a surprise!!!) : DAO and RDO. Additionaly, if you go to MS's web
>page
>>>for VJ, there is an article on VJ 1.1 that also states that JDBC is not
>>>supported. As a matter of fact, we had to pull our JDBC chapters
because
>MS
>>>has dumped support for it and write DAO and RDO chapters.
>>
>>JDBC has worked with Microsoft's Java VM and with Visual J++ since early
on
>
>>
No Spam
Matthew D. Siple wrote:
>
> Martin,
>
> My understanding of J++ is that it is JDK1.01 compliant and implements
> only the parts of JDK1.1 that Microsoft likes. Although they must
> support the entire JDK1.1 according to their contract, they have
> six months after the official release of JDK1.1.to do so.
>
> This is the very reason that JavaSoft is implementing the PURE
> JAVA branding. This type of icompatability across platforms will
> kill Java. (My personal opinion is that this is the very reason
> Microsoft is making it's version incompatible -- divide and conqure )
Indeed. Their decision to not implement JNI is
malicious. It sounds very much like they want to force
those who want cross-platform native libraries to support
both Microsoft's proprietary native code interface and
the standard JNI native code interface.
If Microsoft weren't such a monopoly, I'd say we should boycott
them. But that's not very practical nowadays.
- Dan
--
Reply to dank at alumni.caltech.edu
The opinions expressed in this message are my own,
and are not the opinions of my employer.
Charles Darwin - a guy with a Vastly dangerous idea!