Andreas Tille wrote:
> OK, I could try that but what about the claiming that there is no
> method log() in GenericServlet? Looking into the definition of
> GenericServlet in the Servlet 2.1 API doc and also in GenericServlet.java
> i can see clearly its definition.
Humm I can't see log() method
On Thu, 20 Apr 2000, Edouard G. Parmelan wrote:
> > Found 3 semantic errors compiling "LogWriter.java":
> >
> > 5. public class LogWriter extends PrintStream
> > <--->
> > *** Error: No match was found for constructor "PrintStream()".
>
> Class P
Andreas Tille wrote:
> public class LogWriter extends PrintStream
> {
> public static void SetLog(GenericServlet gs) {
> System.setErr(gs.log);
> }
> }
>
> May be you immediately see the problem why the compiler fails but I'm
> not experienced enough tocope with the following error messag
On Wed, 12 Apr 2000, Tom Tromey wrote:
> So write a PrintStream subclass which calls log(), create it at
> startup from a place where log() is visible, and call System.setOut
> and System.setErr with it as the argument.
Thanks for the hint. I tried
import java.io.*;
import javax.servlet.*;
p
Andreas> OK, I've thought about that, but my problem (as unexperienced
Andreas> Java programmer!) is, that I can't see the log() method in
Andreas> the classes I use.
So write a PrintStream subclass which calls log(), create it at
startup from a place where log() is visible, and call System.setOut
On Wed, 12 Apr 2000, Stefan Gybas wrote:
> So why don't you use log()?
I tried to explain this into the mail to Eric Ravelomanants.
May be it is bad design???
> > System.out(): nowhere ( is this normal ???)
>
> Yes, it has always been this way.
If this was intended by the developers, does t
On Wed, 12 Apr 2000, Eric Ravelomanantsoa wrote:
> Instead of System.out() and/or System.err() use the log() method of the
> GenericServlet abstract class (your Servlet should be a subclass of it). This
> will
> output your stuff in the jserv.log file.
OK, I've thought about that, but my problem
On Wed, 12 Apr 2000, Seth R Arnold wrote:
> But, I can ask a question: rather than depend upon System.out and
> System.err, why not open a brand new file, say /tmp/debugger, and send
> all your debugging there? If you just need the debugging while writing
> your servlets, this might be plenty. If
On Wed, Apr 12, 2000 at 10:45:53AM +0200, Andreas Tille wrote:
> log(): /var/log/jserv.log
So why don't you use log()?
> System.out(): nowhere ( is this normal ???)
Yes, it has always been this way.
> System.err(): nowhere (? formerly it was going to /var/log/apache/error.log
>
Andreas Tille wrote:
> In my system occueses the following:
>
> log(): /var/log/jserv.log
> System.out(): nowhere ( is this normal ???)
> System.err(): nowhere (? formerly it was going to /var/log/apache/error.log
> but now it doesn't 8- )
>
Instead of System.out()
Hello Andreas,
I am sorry, I don't run java servlets, nor do I know where to start. Nor
do I know the answer to your question.
But, I can ask a question: rather than depend upon System.out and
System.err, why not open a brand new file, say /tmp/debugger, and send
all your debugging there? If you
Hello,
unfortunately I was not yet able to solve my realy urgent problem
with logging of JServ messages. Please could anyone who is
running JServ please test the simple example I attached to this
mail.
It just prints a simple debugging line vie log()-method, System.out
and System.err. I really
12 matches
Mail list logo
