[jboss-user] [JBossCache] - Re: Minimizing POJOCache impact on existing codebases

[ben.wang@jboss.com]

Greg,

To answer your questions regarding load-time instrumentation.

1. You will notice in the examples dir, I have not put any load-time examples there. The main reason actually is that we don't encourage load time option for production usage. This is because, say, 1) run under JBoss AS, it will be very slow to start AS because JBoss Aop/Javaassit need to inspect all of the classes involved, and 2) under other AS envs, no way we can have our own special class loader without servere tinkering.

So unless you run it as a standalone, load-time option is not that good. You will notice that Terracotta has had vendor specific start up scripts, of which is a pain, IMO. 

And honestly, I don't see the downside of using AOPC for production. Do you see one?

2. So like you mentioned, it is good to learn this product using load-time option. I agree. Actually, I use the following Java options to run the unit test inside my IDE:

-Djboss.aop.path=${output}/resources/jboss-aop.xml -javaagent:${lib-50}/jboss-aop-jdk50.jar

So can you possibly contribute an example that runs with load time? :-)

3. Finally, PojoCache with default configuration property (e.g., LOCAL mode) is simply not interesting. You can't see the fine-grained graph replication at work!
 
-Ben
	

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971441#3971441

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971441