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

[gregory.pierce@jboss.com]

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.
  | 
  | 
  |   |    <target name="one.test.aop50" depends="compile, generateClassLoader" description="run one junit test case.">
  |   |      <junit printsummary="yes" timeout="${junit.timeout}" fork="yes">
  |   |         <jvmarg value="-Djboss.aop.path=${output}/resources/jboss-aop.xml"/>
  |   |         <jvmarg value="-javaagent:${lib-50}/jboss-aop-jdk50.jar"/>
  |   |         <classpath path="${output}/etc" />
  |   |         <sysproperty key="log4j.configuration" value="file:${output}/etc/log4j.xml" />
  |   |         <classpath refid="lib.classpath.50"/>
  |   |         <classpath refid="build.classpath.50"/>
  |   |         <formatter type="xml" usefile="true"/>
  |   |         <test name="${test}" todir="${reports}"/>
  |   |      </junit>
  |   |    </target>
  |   | 
  | 
  | 


This simply does not give any realy information without tearing down the build script and makes an assumption that the user knows what the javaagent flag is. Is there an expectation that the user would have gone into the AOP documentation or JVM documentation to try and figure out what this flag is supposed to mean, do, etc?

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

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