New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CXF-7069] Finish JPACodeDataProvider implementation #173
Closed
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
…on a network error
…tch from David Karlsen applied with thanks, This closes apache#142
…, patch from Gary Gregory applied with thanks
…ch from Svetlin Zarev applied with thanks
… property condition as agreed and also updating a scan demo
…re that is build in package phase for -Pfastinstall to work. # Conflicts: # systests/transport-undertow/pom.xml
…the full WS-Trust URIs
…g group information
… operation name, removing the optiona query params
… transformed token
…eeded per a single scope
(cherry picked from commit b114d6c)
…asePath mismatch, with thanks to Andriy Redko
…ry can get a useful Connection (cherry picked from commit 2ca0621)
… (with thanks to Francesco)
…date SAML response behind reverse proxy
…upport URL-encoded paths correctly, patch from Tadayoshi Sato applied, This closes apache#164
…er by default, making TikaContent serializable
(cherry picked from commit e32418d)
… payload, patch from Daniel Baumann applied, This closes apache#163
JPAOAuthDataProvider had the following issues : * it is a singleton and uses a shared entityManager for all clients, so we should inject EntityManagerFactory and not EntityManager. * Error when creating a BearerAccessToken during OIDC authorization code flow : insufficient column size for idToken storage. This commit fixes both issues and add : * CMT version of JPACodeDataProvider for container managed entityManager * Hibernate and OpenJPA unit tests
Some tweaks to use Open JPA : * jpql modification (JPA compliance) * ensure entity associations are managed before merging/persisting. * added runtime bytecode weaving
Closed as too old pr |
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 resolves the following issues :
JPACodeDataProvider has now :
In this version, transactions are managed by JPACodeDataProvider.
In this version, transactions are managed by the container (i.e. Spring).
Tests have been added to check both Hibernate and OpenJPA compliance.
Bad news is that overall performance is not quite good.
Here's the number of request issued for basic OIDC / Oauth2 interactions :