spring-projects / spring-projects/spring-data-mongodb
DefaultDbRefResolver swallows exceptions [DATAMONGO-1111]
@odrotbohm is already working on this.
Since Dec 30, 2020.
- Dominant language
- Java
- Stars
- 1.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Pablo Díaz-López opened DATAMONGO-1111 and commented
While doing some caching at DBRef resolve (workaound for DATAMONGO-1071), we found that in MongoExceptionTranslator is swallowing the stacktrace of an exception we throw.. In fact it also swallows the exception if for example the proxy of a DBRef lazy field cannot be instantiated, which will throw a MappingInstantiationException.
As I read from javadoc MongoExceptionTranslator should work this way, the problem seems to be at DefaultDbRefResolver.resolve(), because it sets the translatedException as cause which can be null if not translated.
Affects: 1.6.1 (Evans SR1)
1 votes, 2 watchers
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.