Hi christopher This wasn't the case, just there was nothing else back. I managed to see it using a separate log4j configuration and adding debug to the org.spring. There is a listener inside spring that when it fails no message is shown...
regards 2008/10/21 Christopher Schultz <[EMAIL PROTECTED]>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Emerson, > > emerson cargnin wrote: >> What is the right approach to show the deployment errors? > > This error: > >> SEVERE: Context [/search] startup failed due to previous errors > > Indicates that the original error is /before/ this message in the log > file. So, look backward through catalina.out to see what happened. If > might help to delete catalina.out and start with a fresh one just so you > can see what the new messages are (or, you could just look at the > timstamps). > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkj9P0cACgkQ9CaO5/Lv0PAzaACcD9e5a92SCilgXflmNWrHB9ta > EAIAnijGj5kC7/nLJiDFdF10SzZDQc3v > =8yVC > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
