DATAMONGO-884 - Improved handling for Object methods in LazyLoadingInterceptor. #158
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
March 28, 2014 14:27
Prepare issue branch.
thomasdarimont
pushed a commit
that referenced
this pull request
Mar 28, 2014
…terceptor. We now handle invocations of equals/hashcode/toString Object methods that are not overridden with custom proxy aware logic. This avoids potentially NPEs and makes it easier to debug code that deals with proxies (due to a proper toString representation of a proxy). Original pull request: #158.
thomasdarimont
pushed a commit
that referenced
this pull request
Mar 28, 2014
…terceptor. We now handle invocations of equals/hashcode/toString Object methods that are not overridden with custom proxy aware logic. This avoids potentially NPEs and makes it easier to debug code that deals with proxies (due to a proper toString representation of a proxy). Original pull request: #158.
thomasdarimont
pushed a commit
that referenced
this pull request
Mar 28, 2014
…terceptor. We now handle invocations of equals/hashcode/toString Object methods that are not overridden with custom proxy aware logic. This avoids potentially NPEs and makes it easier to debug code that deals with proxies (due to a proper toString representation of a proxy). Original pull request: #158.
…terceptor. We now handle invocations of equals/hashcode/toString Object methods that are not overridden with custom proxy aware logic. This avoids potentially NPEs and makes it easier to debug code that deals with proxies (due to a proper toString representation of a proxy). Original pull request: #158.
thomasdarimont
pushed a commit
that referenced
this pull request
Mar 31, 2014
…terceptor. We now handle invocations of equals(…)/hashCode()/toString() methods that are not overridden with custom proxy aware logic. This avoids potentially NullPointerExceptions and makes it easier to debug code that deals with proxies (due to a proper toString representation of a proxy). Original pull request: #158.
thomasdarimont
pushed a commit
that referenced
this pull request
Mar 31, 2014
…terceptor. We now handle invocations of equals(…)/hashCode()/toString() methods that are not overridden with custom proxy aware logic. This avoids potentially NullPointerExceptions and makes it easier to debug code that deals with proxies (due to a proper toString representation of a proxy). Original pull request: #158.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We now handle invocations of equals/hashcode/toString Object methods that are not overridden with custom proxy aware logic. This avoids potentially NPEs and makes it easier to debug code that deals with proxies (due to a proper toString representation of a proxy).