Using bytecode instrumentation in application servers and frameworks
"Kuperberg, Michael" <[email protected]>
| Newsgroups | gmane.comp.java.objectweb.asm |
|---|---|
| Organization | Universitaet Karlsruhe (TH) |
| Message-ID | <14979508.358.1273507735376.JavaMail.open-xchange@iragroupware> |
Hi all, using java.lang.instrument package, it is possible to specify an load-time instrumentation agent for "standard" Java programs, i.e. Java SE. Does anybody have experience with agent-based instrumentation of Java EE (enterprise edition) or Spring framework applications? Reusing java.lang.instrument would be an option, but the agent needs to be configured to distinguish the application classes (that I want to instrument) from the middleware classes (that shouln't / cannot be instrumented). I would like to use load-time instrumentation as "the last in the chain" agent so that BCI performed by the app server itself is covered. The Java EE specification seems not to have an own mechanism; vendor-specific interfaces (if any) are hard to find. Does anybody have experience/suggestions/ideas about bytecode instrumentation in scenarios other than Java SE? Any help will be appreciated :-) Many thanks, Michael Kuperberg
message-footer.txt
(text/plain, 238 B)
-- You receive this message as a subscriber of the [email protected] mailing list. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws