> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 15, 2000 4:15 AM
> To: [EMAIL PROTECTED]
> Subject: JESS: JDK 1.1 support in Jess 6
>
>
> Hi Folks,
>
> I'd like some opinions on the idea of dropping Java 1.1 support in
> Jess 6 - i.e., using some Java 2 features. These might include
> Collections, Swing, weak references, Remember that the final
> Jess 6 release is still some time in the future. While you're at it,
> what do you think about using features introduced in JDK 1.3 - i.e.,
> dropping support for JDK 1.2? This would let me use the new dynamic
> proxy class stuff. I guess my personal opinion is that I should drop
> 1.1 support, but not 1.2 yet. What do you think?
We use Microsoft's Visual J++ because of its easy COM
integration, the ability to use its J/Direct mechanism to
call out to dll exported functions without resorting to JNI,
and the qualities of the development environment.
This product (VM) is however at the JDK 1.1 level. One can
easily use the util classes from the jdk 1.2, and can also use
Swing1.1.1. However, Weak references, some of the security
features, etc. won't work. (For example, I've been unable to
get things like Jini or JAIAPI to work with the MS VM. - if
anybody knows a way to do this please let me know -- approaches
I've tried inevitably lead to the Sun supplied classes trying
to make VM specific native calls, which results in loading
the Sun VM into the MS VM with the expected devastating results).
If these features are used in future Jess versions, MS VM's
would seem to be cut out of the set of possible working
environments.
-- Dan
---------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the
list (use your own address!) List problems? Notify [EMAIL PROTECTED]
---------------------------------------------------------------------
