| java.lang.Object
 org.codehaus.aspectwerkz.extension.jrockit.JRockitPreProcessor
| JRockitPreProcessor | | public class JRockitPreProcessor implements com.bea.jvm.ClassPreProcessor(Code) | | JRockit (tested with 7SP4 and 8.1) preprocessor Adapter based on JMAPI JRockit has a low
level API for hooking ClassPreProcessor, allowing the use of online weaving at full speed.
Moreover, JRockit does not allow java.lang.ClassLoader overriding thru -Xbootclasspath/p option.
The main difference with standard AspectWerkz online mode is that the ClassPreProcessor
implementation and all third party jars CAN reside in the standard classpath. The command
line tool will look like:
"%JAVA_COMMAND%" -Xmanagement:class=org.codehaus.aspectwerkz.extension.jrockit.JRockitPreProcessor
-cp "%ASPECTWERKZ_HOME%\target\aspectwerkz-extensions-%ASPECTWERKZ_VERSION%.jar;%ASPECTWERKZ_HOME%\lib\aspectwerkz-core-%ASPECTWERKZ_VERSION%.jar;%ASPECTWERKZ_HOME%\lib\aspectwerkz-%ASPECTWERKZ_VERSION%.jar;%ASPECTWERKZ_LIBS%"
-Daspectwerkz.home="%ASPECTWERKZ_HOME%" -Daspectwerkz.transform.verbose=yes %*
Note: there can be some NoClassDefFoundError due to classpath limitation - as described in
http://edocs.bea.com/wls/docs81/adminguide/winservice.html In order to use the BEA JRockit
management server (for further connection of management console or runtime analyzer), the regular
option -Xmanagement will not have any effect. Instead, use -Dmanagement.
author:
Alexandre Vasseur
author:
Jonas BonŽr |
| JRockitPreProcessor | | public JRockitPreProcessor()(Code) | | The JMAPI ClassPreProcessor must be self registrating
|
| preProcess | | public byte[] preProcess(ClassLoader caller, String name, byte[] bytecode)(Code) | | Weave a class
Parameters:
caller - classloader
Parameters:
name - of the class to weave
Parameters:
bytecode - original bytecode weaved |
|
|