cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sberyozkin <...@git.apache.org>
Subject [GitHub] cxf issue #273: lock RefreshToken entity with pissimistic locking to avoid c...
Date Fri, 19 May 2017 10:14:03 GMT
Github user sberyozkin commented on the issue:

    https://github.com/apache/cxf/pull/273
  
    Viacheslav, the patch has been applied with minor updates to let people use a Java lock
if they prefer (JPA2 provider is currently using the pessimistic lock as per your code).
    
    However the test fails so I disabled it - can you please have a look and also copy it
it to JPACMTOAuthDataProviderOpenJPATest class to make sure it works with OpenJPA - to make
sure we don't break the JPA2 provider depending on OpenJPA ? Thanks


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message