openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pinaki Poddar <ppod...@apache.org>
Subject Re: [jira] Commented: (OPENJPA-980) EhCache implementation of OpenJPA caching
Date Mon, 16 Mar 2009 20:06:33 GMT


The core strength of an open source project is participation of a community
of users and contributors. OpenJPA is no exception and will be enriched by
facilitating individual contributors. How we can facilitate such a process
with due regard to the concerns you raise is the purpose of OPENJPA-979. As
it is noted in OPENJPA-979, that there must be a distinction in terms of
responsibility/warranty of core assets and contributions. The exact nature
of such distinction needs to fleshed out.



JIRA jira@apache.org wrote:
> 
> 
>     [
> https://issues.apache.org/jira/browse/OPENJPA-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682394#action_12682394
> ] 
> 
> Kevin Sutter commented on OPENJPA-980:
> --------------------------------------
> 
> 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
> 
>> EhCache implementation of OpenJPA caching
>> -----------------------------------------
>>
>>                 Key: OPENJPA-980
>>                 URL: https://issues.apache.org/jira/browse/OPENJPA-980
>>             Project: OpenJPA
>>          Issue Type: New Feature
>>          Components: datacache
>>    Affects Versions: 1.2.0
>>            Reporter: Craig
>>
>> 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!
> 
> -- 
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
> 
> 
> 

-- 
View this message in context: http://n2.nabble.com/-jira--Created%3A-%28OPENJPA-980%29-EhCache-implementation-of-OpenJPA-caching-tp2487341p2488152.html
Sent from the OpenJPA Developers mailing list archive at Nabble.com.


Mime
View raw message