Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve/unify debug logging at BeanDefinitionReader and BeanFactory level [SPR-17090] #21627

Closed
spring-issuemaster opened this issue Jul 26, 2018 · 1 comment
Assignees
Milestone

Comments

@spring-issuemaster
Copy link
Collaborator

@spring-issuemaster spring-issuemaster commented Jul 26, 2018

Marten Deinum opened SPR-17090 and commented

There are several implementations of the BeanDefinitionReader interface (as well as the ConfigurationClassBeanDefinitionReader. Each of them has some sort of DEBUG/TRACE logging however each does log different things. 

Some do log the resource read (properties based), others don't. Others do log the number of bean definitions read (groovy) others don't. Would be nice if the messages from the different implementations would be unified somehow. Like at least that each reader shows the resource being read and number of beans for instance and also on a consistent level. 

 

This relates to the more general ticket #21485 regarding improving logging. 


Affects: 4.3.18, 5.0.7

Issue Links:

  • #21485 Improve logging for development (DEBUG vs TRACE)

Referenced from: commits f13f041, c037e75

@spring-issuemaster
Copy link
Collaborator Author

@spring-issuemaster spring-issuemaster commented Jul 27, 2018

Juergen Hoeller commented

I'm extending the scope of this ticket towards a refined debug/trace logging experience for bean definition reading as well as bean factory initialization in general, i.e. a debug log setting at the org.springframework.beans package level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.