Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Someone where i work noticed (in stacktrace) that when running the jvm with -javaagent:spring-instrumentation.jar my JAXB annotated classes have strange new methods in them which we didn’t write: e.g. SomeJaxbAnnotatedClass$JaxbAccessorM_getFields_setFields_java_util_Set.get
Does this mean that jaxb uses bytecode instrumentation when it is available? Where can i read more about this functionality?
Thanks,
Yuval
Just an addition to skaffman’s post:
What you see (SomeJaxbAnnotatedClass$JaxbAccessor…) is an inner class, which is generated dynamically by the JAXB reference implementation. To prevent reflection overhead at runtime, bytecode for the concrete implementations of the class
com.sun.xml.bind.v2.runtime.reflect.Accessorare generated and injected into the current classloader by invoking ClassLoader.defineClass(String, byte[], int, int), after using reflection to circumvent the protected access modifier of the defineClass method.So, the JAXB reference implementation is not instrumenting bytecode in the sense that it’s modifying existing classes, but generates new classes for optimized runtime performance.