Introduced Arquillian-based example for JPA 2.1 custom converter feature #218
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
…ure. This project demonstrates following new additions to JPA 2.1 * Custom converter for `CreditCard` object which belongs to Employee * JPA 2.1 schema generation / db seeding options (see `persistence.xml`) In addition to Arquillian following tools has been used: * AssertJ fluent assertions to verify the result of retrieving all objects from the datastore * ShrinkWrap Maven resolve to bundle AssertJ with test deployment
arun-gupta
added a commit
that referenced
this pull request
May 5, 2014
Introduced Arquillian-based example for JPA 2.1 custom converter feature
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 project demonstrates following new additions to JPA 2.1
CreditCardobject which belongs to Employeepersistence.xml)In addition to Arquillian following tools has been used:
I have removed derby from global dependencies, as it was leading to
java.lang.SecurityException: sealing violation: package org.apache.derby.impl.jdbc.authentication is sealedwhen running on Glassfish Embedded. @arun-gupta please let me know if that is safe.