This is somewhat off topic, but the whole VM issue on Linux seems to be
somewhat up in the air right now. This was recently discussed in length at
slashdot. The IBM port is only at 1.1.8. Blackdown's support for 1.2.2 is
still in beta. Bugs in Sun's 1.2.2 port were reported, but seemed to
primarily effect AWT support. Processors other than x86 also aren't
supported by the port. I was pretty content with IBM's until a JDBC driver
crashed it yesterday. But, overall it seems that 1.1 is still the best
performing option on the widest range of platforms.
I'd be curious to know what 1.2 features you are interested in using in
Turbine. Since 1.1 code can run on a VM of either version, it still seems
like the best option.
BTW, is anyone using a JDBC driver for access to MS SQL 7.0 with village?
I was hoping to use FreeTDS, but it doesn't seem to support meta data. I
also attempted to use both BEA and Ashna's drivers. Both of which returned
null when asking for the table name from a meta data of a recordset. This
caused village to throw and a null pointer exception and I'm still trying to
determine if it is problem with the driver or with my code. It would be
nice to know that the driver worked properly.
~christopher
----- Original Message -----
From: John McNally <[EMAIL PROTECTED]>
To: Turbine <[EMAIL PROTECTED]>
Sent: Thursday, February 17, 2000 9:08 AM
Subject: jdk1.1 compatibility requirement.
> Now that Sun has released a production version of JDK1.2.2 for Linux,
should
> we start consideration of dropping jdk1.1 conformance from Turbine's
> requirements? Or are we still waiting for any other os's?
>
> <http://www.javasoft.com/products/jdk/1.2/download-linux.html>
>
> John McNally
>
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
