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

2006-09-20 Thread [EMAIL PROTECTED]
"[EMAIL PROTECTED]" wrote : | I am working on that very thing. Actually putting together a whitepaper that speaks to JBossCache specifically. | Good! The example POJOs are located under examples distro. There is actually a loodtime directory that is using the special classloader (except it

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

2006-09-19 Thread [EMAIL PROTECTED]
"[EMAIL PROTECTED]" wrote : 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

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

2006-09-13 Thread [EMAIL PROTECTED]
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 wil

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

2006-09-13 Thread [EMAIL PROTECTED]
Further take a look at this paragraph in the documentation anonymous wrote : | In this chapter, we explain how to instrument (or "aspectize") the POJOs via JBossAop. There are two steps needed by JBossAop: 1) POJO declaration, 2) instrumentation. But depends on the JDK and instrumentation mod

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

2006-09-13 Thread [EMAIL PROTECTED]
Note, that is the only information in the documentation at all with respect to special classloader/javaagent. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971340#3971340 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p

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

2006-09-13 Thread [EMAIL PROTECTED]
I went to the POJOCache documentation and looked for the javaagent information and found the following: anonymous wrote : | If you are running JDK5.0, you can also use the javaagent option that does not require a separate Classloader. Here are the ant snippet from one-test-aop50, for example

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

2006-09-11 Thread [EMAIL PROTECTED]
To answer your questions: 1. There are two ways to instrument your POJO: compile time (a la aopc) and load time (a la -javaagent option for special classloader). I believe Terracotta also uses the latter approach. 2. BTW, the proper PojoCache doc is under: [url]http://labs.jboss.com/file-access