|
Re: CacheInterceptor [message #1061875 is a reply to message #1060988] |
Tue, 04 June 2013 13:23 |
|
Not sure I understand what you are trying to do? EclipseLink supports cache coordination through RMI and JMS (and JGroups support is under development in EclipseLink 2.6).
EclipseLink has its own cache, how are you trying to use EhCache and for what purpose?
Integrating with a third party cache can be complicated, more than just extending CacheInterceptor is required. What have you done so far?
For updates EclipseLink will acquire a lock on the cache key, then update the cached object directly, then release the lock. EclipseLink has a "live" object cache,
so has a different model than get/put as the objects in the cache are interrelated and object identity is maintained.
So if you are putting the object directly in the EhCache they will get update without a put call. You could potential call put from your CacheKeyInterceptor's release method.
But you probably need to put a copy of the object stripped of its relationships in the EhCache. How do you intend to configure EhCache?
Are you using EhCache just as a local cache, or are you trying to use its replicated cache support? How do you intend to serialize your objects if trying to replicate?
James : Wiki : Book : Blog : Twitter
|
|
|
|
Re: CacheInterceptor [message #1062978 is a reply to message #1062444] |
Tue, 11 June 2013 15:05 |
|
Ehcache replication I believe works with RMI, JGroups, and JMS, similar to EclipseLink. What type of replication are you using?
If you are having issues with JMS, try using RMI instead. EclipseLink 2.6 development stream also has support for JGroups.
James : Wiki : Book : Blog : Twitter
|
|
|
Powered by
FUDForum. Page generated in 0.01546 seconds