Now we are talking! I've been wanting to use the instrumentation stuff
in our Avalon-based product for a while but just haven't gotten around
to it and didn't want to tie into it too directly. I'll catch up with on
the Avalon lists... however it would still be cool for a J2EE server as
well :-)
Robert
Berin Loritsch wrote:
Robert McIntosh wrote:
Now, if the J2EE container used this (or a similiar) system in a
non-intrusive way, say via interceptors ala JBoss, that would be
really nice. You could have the turn on/off feature and not have to
implement or extend any classes/interfaces. Would make a nice
addition to an admin console as well.
Completely doable!
The whole API was designed to have little or no impact if there is no
Instrumentation Manager available, or no client connected. It uses the
same principles as the Logger interfaces in JDK 1.4/Log4J/LogKit tools
to skip the overhead as early as possible.
If you're interested, I can help you with the integration. The
InstrumentationManager supports pluggable "transports" to connect to
clients, so if you want to make the manager connect with something other
than AltRMI, I can do my best to help.
