Build #192

Plan branch:

Build: #192 was successful Scheduled with changes by GregDThomas <greg.d.thomas@gmail.com>

Code commits

Openfire (master)

  • GregDThomas <greg.d.thomas@gmail.com>

    GregDThomas <greg.d.thomas@gmail.com> 31b1325ce3c877314f442044284701f567286174

    Merge pull request #1305 from GregDThomas/improved-cache-lock-api
    OF-1712: Introduce a new API to provide locking of Cache entries.

  • GregDThomas <greg.d.thomas@gmail.com>

    GregDThomas <greg.d.thomas@gmail.com> c77d75794658f6991178948374cb9728c10ca752

    Introduce a new API to provide locking of Cache entries.
    Why? The single responsibility principle. It makes more sense (to me)
    to ask the Cache to lock a key rather than the CacheFactory, which should
    concentrate on creating cache's.

    Note that only the API changes; the implementation still resides in
    CacheFactory. Easiest to leave it there until the deprecated method is
    removed.

    • xmppserver/src/main/java/org/jivesoftware/util/cache/Cache.java (version c77d75794658f6991178948374cb9728c10ca752)
    • xmppserver/src/main/java/org/jivesoftware/util/cache/CacheFactory.java (version c77d75794658f6991178948374cb9728c10ca752)