Feature/278 immutable datatypes #280
Merged
Conversation
This file contains 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
… into feature/278-immutable-datatypes # Conflicts: # jopa-impl/src/main/java/cz/cvut/kbss/jopa/sessions/CloneBuilder.java
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.
This PR fixes #278 which allows new datatypes like
java.util.Localeto be stored when a Converter is specified. This is done by assuming every type that is not managed by JOPA itself or that has a special builder defined in the JOPA codebase like Maps and Collections, is immutable.It also improves the error shown when the
@Convertannotation is missing by fixing aNullPointerException.References to
DateInstanceBuilderwere also removed, because the special handling for Dates is no longer needed.