[JBoss JIRA] Closed: (JBCACHE-545) Consider removing TreeCache, parent, and name
by Manik Surtani (JIRA)
[ http://jira.jboss.com/jira/browse/JBCACHE-545?page=all ]
Manik Surtani closed JBCACHE-545.
---------------------------------
Resolution: Done
name and parent have been removed.
A cache reference is necessary since we now allow calls directly on the node, which means they need to be routed via cache (for the time being) to go through the interceptor stack. Will change in 2.1.0 when we use a proper AOP framework rather than our own handwoven interceptors.
> Consider removing TreeCache, parent, and name
> ---------------------------------------------
>
> Key: JBCACHE-545
> URL: http://jira.jboss.com/jira/browse/JBCACHE-545
> Project: JBoss Cache
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Affects Versions: 1.3.0.GA
> Reporter: Elias Ross
> Assigned To: Manik Surtani
> Fix For: 2.0.0.ALPHA2, 2.0.0.GA
>
>
> "name" is redundant with respect to Fqn, which contains the name already
> parent can be obtained in O(log(n)) time with a TreeCache instance
> TreeCache can be passed in from the user to methods that require it
--
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
17 years, 3 months
[JBoss JIRA] Closed: (JBCACHE-270) Create a notification interceptor
by Manik Surtani (JIRA)
[ 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
17 years, 3 months