-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
From: jon * <[EMAIL PROTECTED]>
> hey everyone,
>
> we need some feedback on 1.1b1...your "constructive" and "detailed"
feedback
> helps us improve the product. if you keep it to yourself, then the product
> never gets better. ;-)
ok, here we go
> how is it working for you?
like a charm. and no problems (until now, at least) with the servlets pool.
we run our in-house servlets, gsp *and* jsp (for performance and
funcionality benchmarking, not for development), everything is fine -- you
guys rock!
> do you like the new installation process?
the one thing i like best is the fact that the 1.0 installation (for unix)
made all configuration files point to the *.properties and *.conf files in
the source tree. which usually means a root-only writable directory, which,
guess what, apache+jserv cannot write into. so no logs. and jserv does not
like that. now, when i finished compiling, typed in the usual 'make install'
and said to myself 'geesh, gotta fix those pesky conf files yet again',
surprise, surprise, it was all ready! i just had to chown the installation
directory to the webserver's user and voilá! jserv works!
> what sort of problems did you run into?
as stated before, none. but do not use the load balancing features (which
seem to the bleeding edge on jserv development these times). we did a Stupid
Thing[tm], however, which was to use 'configure --with-apache-src' pointing
to a previously-built-with-jserv-1.0 apache source tree. the result was a
jserv-1.0-enable apache, of course, but before that we spent tons of time
trying to understand why jserv was complaning about 'Unknown protocol
(ajpv12)'. So, guys, remember to do a 'make clean' (or better yet, remove
and re-untar the apache source tree) before 'make install'ing jserv-1.1 on a
previsouly 1.0-built apache tree
> was there anything missing from the docs/upgrade.html?
none i noticed.
> what was the hardest part about the upgrade?
i found it so much easier than jserv-1.0, i really think the hardest part
was looking around to see if i was missing anything... =)
> what was the easist part?
definitely not having to mess with the conf files for fixing the paths. i
used to grep the conf files for '/usr/local/src' to look for bad paths.
farewell to that. with no looking back, thank you!
btw, just a few comments: the servlets names for GSP and JSP have changed
since the original jserv.conf was written. I know this is homework for those
working with these technologies, but anyway... the correct ApJServAction
lines for the current versions of JSPServlet and GspServlet are
ApJServAction .jsp /servlets/org.gjt.jsp.JSPServlet
ApJServAction .gsp /servlets/com.bitmechanic.gsp.GspServlet
if anyone cares to have the official jserv.conf fixed...
> thx.
>
> -jon
keep up the great work, guys. you rock.
[]'s
Ulisses Montenegro
NEWStorm -- http://www.newstorm.com.br/
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
