You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the mailing list, good suggestion for using the JDK instrumentation:
The implementation Ive built uses JDK instrumentation to find all loaded classes and inspect for annotations. It seems to work, and takes about 1sec to do its job.
i) The Instrument class - export as jar file with MANIFEST.mf like in ii)
import java.lang.instrument.*;
public class Instrument {
public Instrument() {
super();
// TODO Auto-generated constructor stub
}
private static Instrumentation inst;
public static Instrumentation getInstrumentation() { return inst; }
public static void premain(String agentArgs, Instrumentation inst) {
System.out.println(inst.getClass() + ": " + inst);
Instrument.inst = inst;
}
}
loading of empire configuration from a jar, closed by 62c70f4. also settling on the conventional name for the configuration file and format, noted in the docs on the wiki, we've deprecated trying a bunch of different file names and will remove this in a later version. also adding a new annotation provider based on empire being the java agent for the application and it will load the information about what classes are annotated with what based on what the JVM told the instrumentor on startup. This will override any annotation provider specified in the configuration when used. closed by 62c70f4
From the mailing list, good suggestion for using the JDK instrumentation:
The implementation Ive built uses JDK instrumentation to find all loaded classes and inspect for annotations. It seems to work, and takes about 1sec to do its job.
i) The Instrument class - export as jar file with MANIFEST.mf like in ii)
ii) the Manifest
iii) jvm option : -javaagent:c:\tmp\instrument.jar
iv) From the EmpireAnnotationProvider impl
The text was updated successfully, but these errors were encountered: