Hi Berin, your explanation sounds very interesting. I try to get this up and running just to show the team the power that can be achived using an Avalon framework.
>>[...] > > Instrument is broken up into three packages. > > Instrument (AKA Instrument Client) is used for your > components to define > the "instrument points", or the values you are exposing to the outside > world. > > Instrument Manager is used internally with Fortress so that you can > expose those instrumenation points outside the JVM. To do that, just > adjust the "instrument" configuration file in the connectors > like this: > <connectors> > <connector class="altrmi" port="15555"/> > </connectors> > If you don't want to expost that port, just comment out the connector. OK, do I have to put this as child in the xconf or is there a separate config file? If I use this, I must also have the AltRMI archives added somewhere in the classpath for my webapp (works currently without)? For Merlin I saw in a config file an entry for the host .. do I have to config this now, too? > Instrument Client is the GUI that connects to the running > JVM. In this > case, it will connect to port 15555 (the default) to localhost, and > you will be able to see all your instrument points--plus the ones that > are automatically created for you. > > In a running servlet, you can connect and disconnect the > client at will, > which is a great debugging tool. I also understand you can invoke the > garbage collector in the remote JVM (tres cool). Very cool. Regards, J�rg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
