OpenJPA
  1. OpenJPA
  2. OPENJPA-980

EhCache implementation of OpenJPA caching

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.2.0
    • Fix Version/s: None
    • Component/s: datacache
    • Labels:
      None

      Description

      I created QueryCache and DataCache implementations for EhCache. I think it would be great to see this included in a future version of OpenJPA, as presently, OpenJPA includes only its own implementation.

      The code is licensed under the APL 2.0 and includes unit tests.

      My implementation is based on the work of Pinaki Poddar, who created a DataCache implementation for Coherence - I think that would also be nice to include.

      http://candrews.integralblue.com/2009/03/ehcache-implementation-of-openjpa-caching/

      Thanks!

        Issue Links

          Activity

          Hide
          Donald Woods added a comment -

          It is available from the Ehcache project at - http://ehcache.org/documentation/openjpa_provider.html

          Show
          Donald Woods added a comment - It is available from the Ehcache project at - http://ehcache.org/documentation/openjpa_provider.html
          Hide
          Kevin Sutter added a comment -

          Thanks, Don. I've created the relationship link.

          Show
          Kevin Sutter added a comment - Thanks, Don. I've created the relationship link.
          Hide
          Donald Woods added a comment -

          Believe that is what Pinaki is proposing in OPENJPA-979, that a "contrib" sub-project be created for contributions like this...

          Show
          Donald Woods added a comment - Believe that is what Pinaki is proposing in OPENJPA-979 , that a "contrib" sub-project be created for contributions like this...
          Hide
          Kevin Sutter added a comment -

          I have to question whether OpenJPA is the right repository for these type of plugin implementations. OpenJPA defines and implements the plugin interface, but do we want to be in the "business" of developing and supporting the various plugin implementations? Take this EhCache implementation as an example. I'm sure this implementation provides the level of function required by the submitter. But, how do we know it's a general solution that can be used outside of the submitter's environment and needs? And, do we plan to sign up for support for this implementation? What version(s) of EhCache does this plugin work with? And, who's going to support the next version (or past versions) of EhCache?

          IMHO, the implementation of a plugin should be provided with the product that is being plugged in. In this particular example, should this EhCache implementation be owned by the EhCache team? Now I know this particular case probably won't fly, since Gavin probably doesn't want to promote the use of OpenJPA... But, you get the picture.

          Maybe we should consider a sub-project to house plugin implementations that wish to be supported? Something like OpenJPA-Plugins, or OpenJPA-Caches, or OpenJPA-EhCache (depending on the desired granularity). We just need to be aware of what we're signing up for when we accept contributions like this. Thanks.

          Kevin

          Show
          Kevin Sutter added a comment - I have to question whether OpenJPA is the right repository for these type of plugin implementations. OpenJPA defines and implements the plugin interface, but do we want to be in the "business" of developing and supporting the various plugin implementations? Take this EhCache implementation as an example. I'm sure this implementation provides the level of function required by the submitter. But, how do we know it's a general solution that can be used outside of the submitter's environment and needs? And, do we plan to sign up for support for this implementation? What version(s) of EhCache does this plugin work with? And, who's going to support the next version (or past versions) of EhCache? IMHO, the implementation of a plugin should be provided with the product that is being plugged in. In this particular example, should this EhCache implementation be owned by the EhCache team? Now I know this particular case probably won't fly, since Gavin probably doesn't want to promote the use of OpenJPA... But, you get the picture. Maybe we should consider a sub-project to house plugin implementations that wish to be supported? Something like OpenJPA-Plugins, or OpenJPA-Caches, or OpenJPA-EhCache (depending on the desired granularity). We just need to be aware of what we're signing up for when we accept contributions like this. Thanks. Kevin

            People

            • Assignee:
              Unassigned
              Reporter:
              Craig
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development