Some of that's System.err logging: // log it to System.err System.err.println(message); t.printStackTrace();
https://source.jasig.org/cas3/branches/cas-3_4_x_maintenance/cas-server-3.4.2/cas-server-core/src/main/java/org/jasig/cas/web/init/SafeContextLoaderListener.java Such that no amount of better log4j configuration is going to prevent that crud from showing up in the output from running the unit tests. Have SafeContextLoaderListener and SafeDispatcherServlet outlived their usefulness? At the time I wrote them I was trying to give newcomer deployers who make mistakes in their Spring configuration a better error experience than their whole resulting .war failing to init. Anyway, the test output related to SafeContextLoaderListenerTests appears to be functioning as designed. Andrew On 07/15/2011 04:06 PM, Scott Battaglia wrote: > Those aren't test errors. They are expected log4j output of testing > error handling :-) > > > On Fri, Jul 15, 2011 at 3:58 PM, William G. Thompson, Jr. > <[email protected] <mailto:[email protected]>> wrote: > > ... > > Checked out HEAD. > $ mvn package install > > Builds, but I get a few errors in these tests: > > Running org.jasig.cas.web.init.SafeContextLoaderListenerTests > SafeContextLoaderListener: The Spring ContextLoaderListener we wrap > threw on contextInitialized. > But for our having caught this error, the web application context > would not have initialized. > org.springframework.beans.factory.BeanDefinitionStoreException: > IOException parsing XML document from ServletContext resource > [/WEB-INF/applicationContext.xml]; nested exception is > java.io.FileNotFoundException: Could not open ServletContext resource > [/WEB-INF/applicationContext.xml] > > And all of these are looking for a log4j setup: > Running > > org.jasig.cas.adaptors.x509.authentication.handler.support.CRLDistributionPointRevocationCheckerTests > Running org.jasig.cas.ticket.registry.JBossCacheTicketRegistryTests > Running > org.jasig.cas.ticket.registry.BerkeleyDbTicketRegistryConcurrencyTests > Running > > org.jasig.cas.adaptors.trusted.authentication.handler.support.PrincipalBearingCredentialsAuthenticationHandlerTests > > Are these safe to ignore? Are there some docs on how to get this test > configured properly? If not, any pointers? > > Thanks, > Bill > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
