I am thinking about writing a log file servlet where
I can check the log file of the tomcat session from my
web browser. Thus I do not need to use console and vi
to check it.
Is there already something to do this and I am just
reinvent the wheel or this is totally a bad idea?
If I do this, how
again.
I also publish to another tomcat server and still
have to do the same
thing. On both machines I am running tomcat 5.5.17.
Hope someone has a solution as this is a pain.
Calvin
Tony Smith wrote the following on 5/18/2006 7:30 PM:
Hi,
I am using Tomcat 5.5.9 on Windows. I use
Hi,
I am using Tomcat 5.5.9 on Windows. I use Eclipse to
write my server code. Every time I change my code, I
export the jar directly to the myapp/WEB-INF/lib
directory and restart Tomcat. I found that the new
code is not immediately used by Tomcat, I have to
re-export, re-start Tomcat a
Hi, I run tomcat 5.5 on my computer. If the server
throwed a exception, either because of server side
java code error or because of a jsp error, the
exception was print out in the tomcat log file. I
recently reinstalled tomcat, and found that the
exception is nolonger reported in the log. Why?
Hi,
I am using Tomcat 5.5.9 on Windows. I use Eclipse to
write my server code. Every time I change my code, I
export the jar directly to the myapp/WEB-INF/lib
directory and restart Tomcat. I found that the new
code is not immediately used by Tomcat, I have to
re-export, re-start Tomcat a couple
in my jsp, there is something like:
html:text property=plateDetail.name
value=${plateDetailEditForm.plateDetail.name} /
How can I get this element in javascript? the
following code does not work:
var name =
document.getElementByName(plateDetail.name).value;
I think it is because there is a
It seems that if you have more than three nested
logic:iterate, the code is not going to work.
For example, if you have:
logic:iterate id=p1 name=myForm property=list1
logic:iterate id=p2 name=myForm property=list2
${p2}
/logic:iterate
/logic:iterate
It is ok. But if you have :
