On 5/18/10 1:57 AM, okrohne wrote: > > Hi Donald, > > unfortunatly SQS would not allow to have a transactional cache as there is > a possible delay of 20sec until a message can be fetched and it is designed > that only one instance consumes the message. > > ehcache: Wouldn't the ehcache-jgroups replication > (http://ehcache.org/documentation/distributed_caching_with_jgroups.html ) > do the job as it would propagate put,update,delete to all members. > I assume one need only to configure the cache for svjm and let > ehcache+jgroup do the eviction. > There is already a ehache-openjpa plugin > (http://ehcache.org/documentation/openjpa_provider.html) > What do you think?
Looking at the latest 0.2.0 plugin, it seems to only support the Data/Query cache interface and not the RemoteCommitProvider interface. It includes a noop RCP to use when openjpa.DataCacheManager is set to ehcache. So, are you trying to use a distributed/multi-jvm Data Cache [1] or just remote event notifications [2] w/o caching? If #1, you can use the existing ehcache-openjpa plugin, but #2 will require a new EhcacheRCP to be created.... [1] http://openjpa.apache.org/builds/2.0.0/apache-openjpa-2.0.0/docs/manual/manual.html#ref_guide_cache [2] http://openjpa.apache.org/builds/2.0.0/apache-openjpa-2.0.0/docs/manual/manual.html#ref_guide_event -Donald > > Thanks, > Oliver
