Debugging Spring configuration

Question

I am working on a Java application that uses Spring and Hibernate and runs on a Websphere   I have run into a problem  where I expect Spring to load a Dao into my object  but for some reason that doesn t happen    Another Dao that is specified in much the same way is loaded fine    The question is - how can I debug how Spring decides what to load in   Can I turn on logging for Spring  and where

User · Answer

If you use Spring Boot  you can also enable a    debug    mode by starting your application with a --debug flag   java -jar myapp jar --debug   You can also specify debug true in your application properties   When the debug mode is enabled  a selection of core loggers  embedded container  Hibernate  and Spring Boot  are configured to output more information  Enabling the debug mode does not configure your application to log all messages with DEBUG level   Alternatively  you can enable a    trace    mode by starting your application with a --trace flag  or trace true in your application properties   Doing so enables trace logging for a selection of core loggers  embedded container  Hibernate schema generation  and the whole Spring portfolio    https   docs spring io spring-boot docs current reference html boot-features-logging html

User · Answer

Yes  Spring framework logging is very detailed  You did not mention in your post  if you are already using a logging framework or not  If you are using log4j then just add spring appenders to the log4j config  i e to log4j xml or log4j properties   If you are using log4j xml config you can do some thing like this   lt category name  org springframework beans  gt       lt priority value  debug    gt   lt  category gt    or   lt category name  org springframework  gt       lt priority value  debug    gt   lt  category gt    I would advise you to test this problem in isolation using JUnit test  You can do this by using spring testing module in conjunction with Junit  If you use spring test module it will do the bulk of the work for you it loads context file based on your context config and starts container so you can just focus on testing your business logic  I have a small example here   RunWith SpringJUnit4ClassRunner class   ContextConfiguration locations   classpath springContext xml     Transactional public class SpringDAOTest         Autowired     private SpringDAO dao        Autowired     private ApplicationContext appContext        Test     public void checkConfig                 AnySpringBean bean    appContext getBean AnySpringBean class           Assert assertNotNull bean             UPDATE  I am not advising you to change the way you load logging but try this in your dev environment  Add this snippet to your web xml file   lt context-param gt       lt param-name gt log4jConfigLocation lt  param-name gt       lt param-value gt  WEB-INF log4j xml lt  param-value gt   lt  context-param gt    lt listener gt       lt listener-class gt org springframework web util Log4jConfigListener lt  listener-class gt   lt  listener gt    UPDATE log4j config file    I tested this on my local tomcat and it generated a lot of logging on application start up  I also want to make a correction  use debug not info as  Rayan Stewart mentioned    lt  xml version  1 0  encoding  UTF-8    gt   lt  DOCTYPE log4j configuration SYSTEM  log4j dtd  gt    lt log4j configuration xmlns log4j  http   jakarta apache org log4j   debug  false  gt       lt appender name  STDOUT  class  org apache log4j ConsoleAppender  gt           lt param name  Threshold  value  debug    gt           lt layout class  org apache log4j PatternLayout  gt               lt param name  ConversionPattern                  value   d HH mm ss   p   t   c 3   M   L -  m n    gt           lt  layout gt       lt  appender gt        lt appender name  springAppender  class  org apache log4j RollingFileAppender  gt            lt param name  file  value  C  tomcatLogs webApp spring-details log    gt            lt param name  append  value  true    gt            lt layout class  org apache log4j PatternLayout  gt               lt param name  ConversionPattern                  value   d MM dd yyyy HH mm ss     t   c 5   M   L  m n    gt           lt  layout gt       lt  appender gt        lt category name  org springframework  gt           lt priority value  debug    gt       lt  category gt        lt category name  org springframework beans  gt           lt priority value  debug    gt       lt  category gt        lt category name  org springframework security  gt           lt priority value  debug    gt       lt  category gt        lt category         name  org springframework beans CachedIntrospectionResults  gt           lt priority value  debug    gt       lt  category gt        lt category name  org springframework jdbc core  gt           lt priority value  debug    gt       lt  category gt        lt category name  org springframework transaction support TransactionSynchronizationManager  gt           lt priority value  debug    gt       lt  category gt        lt root gt           lt priority value  debug    gt           lt appender-ref ref  springAppender    gt           lt  --  lt appender-ref ref  STDOUT   gt   -- gt       lt  root gt   lt  log4j configuration gt

[java] Debugging Spring configuration

Examples related to java

Examples related to hibernate

Examples related to spring

Examples related to configuration

Examples related to websphere