Re: JNI runtime library error message

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Hi Jon,

Part of the problem, and the main reason for including our own internal
version of the SDK, is that we have found problems where the Java does not
run correctly with this or that version of JRE/JDK.  Also it eliminates
the necessity of you having an appropriate level of SDK installed.
Remember all the notes on this list alone from people that could not get
parts of ADTS to run because the SDK wasn't installed?  Not everyone is
like you (I put you in the "smart dude" category :-) some of us just
bumble along...

I do appreciate you comment about having several SDK's installed (I also
have several) but I suspect that other developers have found what we have,
that is that SDK's are kinda like different versions of Windows.  They are
all similar but have their own different quirks of implementation.   Maybe
this will all be solved when we move to Linux as the workstation OS ?

Kind regards,

Mike


Mike Hockings, P.Eng.
WebSphere Development Tools for AS/400  -  CODE/Designer & WebFacing !
IBM Canada Ltd. Laboratory
hockings@ca.ibm.com





"Jon Paris" <Jon.Paris@Partner400.com>
Sent by: code400-l-admin@midrange.com
22/04/2002 01:12 PM
Please respond to code400-l


        To:     <code400-l@midrange.com>
        cc:
        Subject:        jni runtime library error message



Hak, rather than simply defaulting to the SDK installed with CODE (isn't
it
supposed to be optional ?) why not do like most other tools and list the
available SDKs and ask me which I want to use.

One of things that bugs me about Java is that for this supposedly portable
language, I now have (at last count) 5 different SDKs and goodness knows
how
many run-times.  I don't need any more "stuff" clogging up my system!

Jon Paris
Partner400