[#1439] Added code branch to deal with JPA-based models separately ... #492
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
…om generic models; so plug-ins like Morphia can deal with their own embedded types
pepite
added a commit
that referenced
this pull request
Dec 30, 2012
[#1439] Added code branch to deal with JPA-based models separately ...
|
Reverting since it breaks the whole test suite. |
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.
...from generic models; so plug-ins like Morphia can deal with their own embedded types
Basically - only uses JPAPlugin.JPAModelLoader when the fixture model is derived from GenericModel; otherwise allow embedded classes to build themselves normally. This fixes Morphia's ModelFactory as well as any other plug-in that requires relationship binding