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 Thu, 18 May 2017 15:43:14 GMT
Github user sberyozkin commented on the issue:

    https://github.com/apache/cxf/pull/273
  
    Hi, thanks for the patch. Can you please consider locking at the AbstractOAuthDataProvider
level instead, so that all its extensions (JPA2, JCache, Ehcache and future ones like Mongo-based)
can benefit ?
    I'd consider introducing 'Object refreshTokenLock' and use it lock at https://github.com/apache/cxf/blob/master/rt/rs/security/oauth-parent/oauth2/src/main/java/org/apache/cxf/rs/security/oauth2/provider/AbstractOAuthDataProvider.java#L211
    
    Let me know please if it works for you


---
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