Re: [Classpathx-xml] gnujaxp with JDK1.1.8

[David Brownell]

I don't happen to have a Windows 1.1 setup,
so no I can't try that.  But back when I did, I
don't ever recall seeing an OS-specific problem
at that level that wasn't caused by something odd
in the compiler (or runtime) class loading setup.

Of course, the way the JRE and JDK installed
there was a bit strange too.  I know other folk
have reported problems wherein they've needed
to install Java classes twice, so that both the
runtime and compiler would _both_ find them.
That sounds like the kind of issue you're having.

- Dave



----- Original Message ----- 
From: "Ma, Steve" <address@hidden>
To: "'David Brownell'" <address@hidden>
Cc: <address@hidden>
Sent: Wednesday, December 05, 2001 10:37 AM
Subject: RE: [Classpathx-xml] gnujaxp with JDK1.1.8


> Yes, I have compiled on Solaris with JDK 1.1.8, and it works fine too.
> However with the same command line, it does not compile on Windows JDK
> 1.1.8.  
> Have you tried compiling on Windows platform?
> 
> Thanks,
> Steve
> 
> -----Original Message-----
> From: David Brownell [mailto:address@hidden 
> Sent: Thursday, November 29, 2001 8:46 PM
> To: Ma, Steve; address@hidden
> Subject: Re: [Classpathx-xml] gnujaxp with JDK1.1.8
> 
> Looks like something odd in your environment, or maybe
> a Win32 issue.  I just tried this on a Linux JDK 1.1.8, and
> it compiled just fine.  You're sure that "gnujaxp.jar" is in
> the current directory, yes?  Not installed in "ext" so jdk 1.2
> picks it up no matter how broken the classpath is?
> 
> By the way, it's a bad idea to pass JDK 1.1.8 "classes.zip"
> to the JDK 1.2 javac!
> 
> FYI I've also put back the source changes (to CVS) that
> prevented compiling with the JDK 1.1.8 javac.  That
> Makefile still has problems (since "javac" behaves so
> differently) but that's for another day (maybe).
> 
> - Dave
> 
> 
> ----- Original Message ----- 
> From: "Ma, Steve" <address@hidden>
> To: "'David Brownell'" <address@hidden>; <address@hidden>
> Sent: Thursday, November 29, 2001 12:14 PM
> Subject: RE: [Classpathx-xml] gnujaxp with JDK1.1.8
> 
> 
> > Just simply trying to import the library and compile the code.  Here is a
> > simple code and command line of what I tried:
> > 
> > 
> > gnuJaxpTest.java
> > -------------
> > import gnu.xml.aelfred2.JAXPFactory;
> > 
> > public class gnuJaxpTest {
> >   public gnuJaxpTest() {
> >   }
> > 
> >   public static void main(String[] args) {
> > System.out.println("Hello World");
> >   }
> > }
> > -------------------
> > 
> > Command line output:
> > ----------------
> > Z:\test\gnujaxp>c:\jdk1.1.8\bin\javac.exe -classpath
> > .;c:\jdk1.1.8\lib\classes.z
> > ip;gnujaxp.jar gnuJaxpTest.java
> > gnuJaxpTest.java:1: Class gnu.xml.aelfred2.JAXPFactory not found in
> import.
> > import gnu.xml.aelfred2.JAXPFactory;
> >        ^
> > 1 error
> > 
> > Z:\test\gnujaxp>c:\jdk1.2.2\bin\javac.exe -classpath
> > .;c:\jdk1.1.8\lib\classes.z
> > ip;gnujaxp.jar *.java
> > 
> > Z:\test\gnujaxp>
> > 
> > ------------------------
> > 
> > Is there something that I'm missing?
> > 
> > steve
> > 
> > -----Original Message-----
> > From: David Brownell [mailto:address@hidden 
> > Sent: Thursday, November 29, 2001 3:04 PM
> > To: Ma, Steve; address@hidden
> > Subject: Re: [Classpathx-xml] gnujaxp with JDK1.1.8
> > 
> > Hmm, I'll have to see what's up.  I'd expect an issue
> > compiling the relse on JDK 1.1 (problem to be fixed),
> > but not actually running it.  I'll send a note when the
> > compile problem is gone, and at that point I'll know it
> > runs there (again :) at least for me.
> > 
> > You're sure you've set the class path up right?  What was
> > the particular "trouble" you had?
> > 
> > - Dave
> > 
> > 
> > ----- Original Message ----- 
> > From: "Ma, Steve" <address@hidden>
> > To: <address@hidden>
> > Sent: Thursday, November 29, 2001 11:53 AM
> > Subject: [Classpathx-xml] gnujaxp with JDK1.1.8
> > 
> > 
> > > Does this release work with JDK1.1.8? I have trouble compiling the
> > > statement:
> > >  
> > > import gnu.xml.aelfred2.JAXPFactory;
> > >  
> > > when using JDK1.1.8, but does not happen with JDK1.2.2 or 1.3.
> > >  
> > > Thanks,
> > > Steve
> > >