Hi everybody,
I have this particular problem.
I am creating a file.It is working in hosted mode means the file is
getting created. But when i deploy my project on tomcat and try to run
the application the file is not getting created
This is my code.
try{
File file1 = new File(C:\\logE.txt);
Ryan schrieb:
I have this particular problem.
I am creating a file.It is working in hosted mode means the file is
getting created. But when i deploy my project on tomcat and try to run
the application the file is not getting created
If we are talking about the application that run in the
Thanks Lothar,
I am talking about server side code here, because the client would
anyway not support writing files.
Problem is how do I view this stack trace of the error .
Where can I view the stack trace.
Any pointers to how to view the stack trace.
regards,
Cherian
On Wed, Sep 17, 2008 at 1:13 PM, Ryan [EMAIL PROTECTED] wrote:
Thanks Lothar,
I am talking about server side code here, because the client would
anyway not support writing files.
Problem is how do I view this stack trace of the error .
Where can I view the stack trace.
Any pointers to
Ryan schrieb:
I am talking about server side code here, because the client would
anyway not support writing files.
Doesn't prevent people from trying ;-)
Problem is how do I view this stack trace of the error .
Where can I view the stack trace.
Any pointers to how to view the stack
Tomcat is keeping it's log-files in tomcat 6.0\logs or /tomcat6/
logs. Look for preferences to know what file that is, but basically
you can just take the file with the last changed-date. Normally
you'll find all Exceptions- or System.out.print-output-messages
there.
P.S. Is Linux your
thanks alex,
I am workng on windows.
Now the problem is that all system.out.println statements written in
classes that extend remoteserviceservlet are not printed in the logs
i.e. stdout file.
Any system.out.println statements written in classes that do not
extend remoteserviceservlet are
Ryan schrieb:
I am workng on windows.
Now the problem is that all system.out.println statements written in
classes that extend remoteserviceservlet are not printed in the logs
i.e. stdout file.
Logging with System.out.println is bad style. Inside a servlet
you better use
Danke Lothar,
I think I should got my answer using
getServletContext().log(...) .This does the job.
I still have to check whether it creates files or not. But atleast it
has started printing statements to the log.
regards,
Cherian
--~--~-~--~~~---~--~~
You
