-
1. Re: Persistence
manik May 30, 2008 4:47 AM (in response to swtet)Are you actually instrumenting your objects, either at compile time or runtime, as per the POJO Cache user guide?
Cache loaders will persist whatever is in the cache - and a properly instrumented object will exist in the cache as a set of primitive values. So if you are seeing the entire object being serialized AND your updates aren't being picked up, I suspect you haven't instrumented your classes properly. -
2. Re: Persistence
swtet May 30, 2008 6:47 AM (in response to swtet)Well, I thought I had them instrumented. I am trying use runtime instrumentation. Is there any way to debug things to see if it is picking up the javaagent and finding the annotated class when it loads?
-
3. Re: Persistence
manik May 30, 2008 9:16 AM (in response to swtet)Set your log4j config to enable TRACE level logging for org.jboss.cache and org.jboss.aop classes and you should see it.
-
4. Re: Persistence
jason.greene Jun 1, 2008 1:51 PM (in response to swtet)What version are you using?
-
5. Re: Persistence
swtet Jun 10, 2008 10:35 AM (in response to swtet)I resolved my issue. Besides the -javaagent, I had to make sure I specified the location of the pojocache-aop.xml file. I ultimately wanted that file to be in my classpath so I had to set "jboss.aop.search.classpath=true" and change the name of the xml file to jboss-aop.xml. I tracked this down by looking at the source code. Is that method of configuration documented somewhere (I couldn't find it) or do you plan to drop support for it in the future?
Thanks -
6. Re: Persistence
jason.greene Jun 13, 2008 11:11 AM (in response to swtet)There are no plans to drop this feature. This reminds me, I have been meaning to enhance aop to allow for loading an aop descriptor of a different name under the classpath.