Since he's using 1.2.1, can he add this to his XML config file?
[attribute name="DeadlockDetection"]true[/attribute]
(replacing brackets with less-than and greater-than, it won't let me post XML)
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871000#3871000
"[EMAIL PROTECTED]" wrote : exists() does *not* go through the interceptor
chain, it will not need to acquire locks etc.
So I'm correct in assuming that the reason exists() doesn't go through the
interceptor chain is that the standard interceptors aren't interested in that
method call?
What abo
I am adding a custom interceptor to my TreeCache, but it does not intercept
exists(Fqn) calls because exists(Fqn) does not call invokeMethod(MethodCall).
Is this just because the standard interceptor chain is not interested in this
method? If so, will this change once the interceptor chain becom
I have a question about how replication works. Say you have 4 replicated
caches: A, B, C and D. Assume also that cache A is the coordinator. When
something is put into cache B and the change gets replicated out to the other
caches, is the change:
1) sent first to the coordinator (A) and then fr
As far as I know, invalidation is scheduled to be included in version 1.2.1 or
1.3; time will tell which.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866169#3866169
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866
I have added a comment to the invalidation feature request
(http://jira.jboss.com/jira/browse/JBCACHE-86)
I also added a new feature request
(http://jira.jboss.com/jira/browse/JBCACHE-88) relating to a remote delegating
CacheLoader implementation.
View the original post :
http://www.jboss.org
an that it is not too hard to implement?
"[EMAIL PROTECTED]" wrote :
| "sdanig" wrote : - Lazy replication. When invalidated/uninitialized nodes
are accessed on the clients, the data is retrieved transparently from the
server cache.
| What do you mean? This is provid
Hi,
We are currently developing a client/server application. The server uses
Hibernate for persistence, with TreeCache for the second-level cache. The
clients need local data caches, and we were thinking that an easy way of
implementing these local client caches might be to replicate the server
Tim -
I can see that it might be implemented as you say, and I've no doubt that
keeping only identifiers or proxy references would solve the problem, but the
requirement that we cache only the latest version of the domain objects arises
directly from the fact that we have to cache them in the f
I've been looking through the code a little. Here's a question for someone more
knowledgeable than I: Given the described scenario, what if all my domain
objects extend some common superclass DomainObject, and I add the DomainObject
class to the Set of immediates (primitives) in org.jboss.cache.
The end goal is not for that last false to be true, so it's not enough for me
to just change that portion of the code. The end goal is that when I implement
custom equality logic in my domain objects, the cache uses that logic to ensure
that only the most recent instance of any given domain obje
I added the following code to the Address class included with JBossCacheAop:
int id = -1;
|public int getId() {
| return this.id;
|}
|public void setId(int id) {
| this.id = id;
|}
|public boolean equals(Object o) {
| if(!(o instanceof Addre
12 matches
Mail list logo
