--
Guenther Wieser <[EMAIL PROTECTED]> wrote:
> --
>
> Maybe the mailing list archive would have helped?
It was, a bit. I found I could get System.out by running JServ in Manual
mode, so at least I can do *some* debugging.
It probably would have been more useful if the search was working. :/
> So here's another version:
> > In the JSDK api in HttpServlet there's the method getServletContext()
> > which returns the current context. The ServletConext then has a method
> > called log(), and guess what, this is the thing you need!
> > It works similar to System.out.println(), the famous debugging method
> > for the real experienced java programmer ;-)
That's right. It works very similarly. It all goes to /dev/null. ;)
> > To make sure that you log file contains the log ouput add/change the
> > following in jserv.properties:
> > log.file=/usr/local/jserv/logs/jserv.trace
> > log.channel.servletLog=true <-- THIS IS THE MOST IMPORTANT ENTRY!!!!!!
> >
> > Make sure that log.file is fully qualified, otherwise you might get in
> > troubles.
> > Of course, set the log.file to what you nedd!
Small section of my jserv.properties:
log.file=/onestep/projects/onestep/jserv.log
log.channel.servletLog=true
These settings are reflected in the /jserv-status/ page, and still nothing
appears in the log file I've specified.
--
Sam Couter [EMAIL PROTECTED]
Internet Engineer
tSA Consulting
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
