> On Mon, 25 Oct 1999, Hartnett wrote:
>
> > This same package was installed on Solaris and its runtime and works
> > fine.
> >
> > This group seems to be quick to jump on someone if it is not JAVA
> Linux
> > related in someone's opinion. I am running Blackdown JAVA 2 on Red
> Hat
> > Linux 6, that sounds like this group to me. I don't see what the
> problem
> > is? I thought the idea of this list is to try to help others, not
> to
> > try to make someone want not to use these products?
>
> I don't think Dustin was really jumping on you, he tried to give you a
> possibility which is what you asked.
>
I personally found Justin's point that the symptoms
> "would sugest that your code is to blame, not the Blackdown JDK (and
your message is > therefore off-topic)."
inaccurate, inappropriate, and rather indulgent. It was indeed quite
appropriate to post Hartnett's question to this list, IMO. It is far
from proven that the problem is not a classpath, library, or even
Blackdown port problem -- yet.
For Hartnett, besides getting to the developers and asking them exactly
how they check for Java 2, a couple of things just off the top of my
head: Try setting the java version explicitly by running the program
with a -Djava.version=1.2 (that should not be necessary as Blackdown's
JVM does this correctly anyway, but what the hell, let's see what
happens). The other place where things could break is in loading certain
JDK1.2 classes, so maybe we could try substituting Blackdown's rt.jar
with the one from the Windows installation, just as an experiment (I've
never done this, but it should work, and may give us further clues).
Also, an accurate dump of your environment, esp. the classpath, may tell
us something.
Good luck,
-Armen
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
