Thank you Ben!
1) Before I go to JIRA, let me make sure we understand each other. I forgot to
clearly mention in my previous e-mail that we don't instrument our classes
currently. They are just Serializable. So in this case does the fact that you
are not intercepting the enum field itself still
I have two unrelated questions, the "enum question" much more pressing.
We have a class with some enum fields. And a clustered AOP cache. Across WAN,
not sure if it matters. When the value of the enum field changes (through
simple assignment), the change is reflected in the local cache, but not
I have the same problem. Not sure why it happens and how I can fix it? I do
need transactions!
I define the lookup class in the cache config file as shown below:
Thanks for your help!
Renata.
|
| org.jboss.cache.JBossTransactionManagerLookup
View the original post :
http://www.jb
I downloaded the latest code, and it solved the problem I had, but I ran into a
new problem.
I added a single field to MySimpleObject class:
private StatusEnum status = StatusEnum.OPEN;
where StatusEnum is:
public enum StatusEnum {
OPEN,
CLOSE
}
When I attempt to cha
Ben, thanks so much! I couldn't find tag (or branch) 1.2.4Alpha in JBossCache,
so I'm going to download the latest. Any word on when 1.2.4 is going to be
released?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3891473#3891473
Reply to the post :
http://www.
I have a very simple example that illustrates the problem I described in my
previous question (Posted: Fri Aug 19, 2005 21:08 PMPost subject: Problem
with caching an object with a complex object graph).
Here is the cached class:
---
This might be a rather involved question, so I'll appreciate any help or idea.
I'm caching objects with several fields that are ArrayLists of objects of the
same class (or classes derived from it). I took care to aspectize (aopc)
everything that lies around, or so I believe. Not to mention all of
Hi,
I apologize if this question doesn't belong on this forum. If so, could you
please point me in the right direction?
Here it is anyway:
When I add exactly the same key/object pair to the TreeCacheAop, the backstore
BDB file keeps growing. There is only one node in the cache, the cache doesn'
Oh, thank you, thank you,thank you!
You guys are awesome, responding so quickly to so many people (not to mention
your great products and impressive documentation)! I only wondered whether
anyone was reading because I had no idea how you managed it.
I opened an issue, but I don't have the autho
I hope someone is reading it... or am I writing to myself?
Anyway, I think this is the problem code (from TreeCacheAop.java):
public void evict(Fqn fqn) throws CacheException {
// We will remove all children nodes as well since we assume all children
nodes are part
// of this "obje
P.S. It appears that for the TreeCacheAop evict() causes complete removal of
the node from the backstore. The regular TreeCache doesn't do it. Is this the
expected behavior? I though eviction only affects the memory cache, but not the
backstore. Is there any configuration that would prevent it f
Thank you Bela!
I tried running the testEvictionWithCacheLoader2 from the CacheLoaderTestBase
class, and it indeed works. Then I modified it like this (because this is the
functionality I'm looking for):
cache.putObject("/first/second/third", "val1"); // stored in cache
loader
cach
A complete TreeCache newby here, so sorry if the questions are less than deep
and meaningful. Also sorry for the long post...
I'm experimenting with the TreeCacheAop, using "replSync-service.xml" from
JBossCache-1.2.1.zip file.
After I evict a node, I expect it to be removed from the memory cache
13 matches
Mail list logo
