Improve exception handling when Hibernate-related bean creation fails #22689
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've run into a nasty issue when working with Hibernate's
@Convert
and Spring Framewok.I used
javax.persistence.@Covert
to transform types and inside of converter class I've declaredDateTimeFormatter
as follows:Application context failed to start with exception
The actual reason, however is illegal pattern
"CyyMMdd"
, namely capital "C".Currently it's impossible to understand the reason from the log. Even if I log all messages and find one written in right place (
SpringBeanContainer::createBean
, catch block), it still gives no clue to understanding of actual reason:It took me about 10 minutes of debugging to understand the root cause, so I propose to help other developers by doing this:
BeanFactory
After I had done this I got real reason into the log: