First of all, thanks to all of you doing great work on Apache-Jserv.
I use it every day and it just keeps on ticking...
 
I compiled and am running 1.1b1 under Solaris 7 and Red Hat 6.0.
 
Compiling went smoothly except a couple small items:
 
1. I still don't understand this one, but you might. No matter what I
did with the "--with-jdk-home" and all the flavors thereof, the configure
kept failing saying it could not find the java compiler. I could run the
compiler within the same bash shell without problem. Then I ended up
opening up permission on the JDK with "chmod a+rx" and all worked
ok. Seems mysterious to me that I could use the compiler within a
shell, but permissions caused a problem as the same user in the
same shell when running configure.
 
2. Under Solaris 7, the older version of "make" (I can't determine exactly
what it is) failed with messages I have seen before when "gmake" fixed
the problem, which it did.
 
3. I'm not sure if this is on purpose, but in the distribution the logfile in
jserv.conf is set to "mod_jserv.log" but within jserv.properties it is
"jserv.log" Like I said, I am not sure if these are intentionally two different
logs or not.
 
4. I was unsure with "--with-apache-src=" if the path should include the
"src" directory or not. I ended up guessing that "src" wasn't necessary,
but was unsure. I like the wording "--with-jdk-home" because I am sure
what that means.
 
5. For some reason, I at first seemed blind to the fact that the jserv
module had to be activated with "--apache-module=...". Somehow I
kept skipping over that in the docs each time I read through to
determine why jserv wasn't part of httpd.
 
Thank you everyone for keeping Apache-Jserv progressing. Hats off
to all of you developers!
 
Frank Morton
 

Reply via email to