Here's a hint...
Create the following two files in your webapp's classes folder with the
following content:
commons-logging.properties
--------------------------
org.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog
simplelog.properties
--------------------
org.apache.commons.logging.simplelog.defaultlog=debug
You will now be confronted with probably *FAR* more logging from Struts
(and everything else) than you'd want... if your running under Tomcat
for instance, you'll see virtually (if not actually) *everything* that
happens in excrutiating detail.
Especially when your having an app startup problem, like the OP is
having, I've found this almost always points me in the right direction
(you will see struts-config parse errors pretty clearly for example).
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM: fzammetti
Yahoo: fzammetti
MSN: [EMAIL PROTECTED]
Graham Leggett wrote:
Hubert Rabago wrote:
The times I came across this, it was related to an error in my
struts-config.xml.
Same with me - and the last time I had problems with struts-config I
managed to find the error by stepping through the struts source code
with a debugger (having long since given up hope on Struts' error
handling).
This time the debugger refuses to stop at the breakpoints at both init()
and doGet(), which leads me to believe Struts isn't running at all.
If I knew whether the message originated in Tomcat or whether the
message originated in Struts, I could cut the problem space in half.
Regards,
Graham
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
