[
http://jira.jboss.com/jira/browse/JBCACHE-270?page=all ]
Manik Surtani closed JBCACHE-270.
---------------------------------
Fix Version/s: 2.0.0.GA
(was: 2.1.0.GA)
Resolution: Partially Completed
Moved this to 2.0.0, and fixed.
You now have 2 ways of emmitting notifications (both via the o.j.c.notifications.Notifier
class, obatined via CacheSPI.getNotifier()) - either immediately (causes the Notifier to
call callbacks on all registered listeners) or by putting it on a queue.
The queue is processed by a notification interceptor, as the invocation leaves the chain
(for non-tx calls) or when a tx commits.
At the moment though, notifications are still placed on the queue by code in the
Cacheimpl, OptimisticNodeInterceptor, OptimisticCreateIfNotExistsInterceptor and
CacheLoader/Store interceptors, which isn't ideal, but at least it is a start.
Create a notification interceptor
---------------------------------
Key: JBCACHE-270
URL:
http://jira.jboss.com/jira/browse/JBCACHE-270
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 1.2.4beta
Reporter: Hany Mesha
Assigned To: Manik Surtani
Fix For: 2.0.0.GA
The need has arised to create a notification interceptor to handle the callbacks results
from different method call events and interceptors emitted events.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira