I would prefer to drop this as the JMS monitoring is not being maintained, is not implemented consistently across all interceptors, and unecessarily propagates a dependency on JMS. A better way to achieve the same effect is to use trace level logging with the statistics objects as the msg and use a JMS appender to collect this information.
----- Original Message ----- From: "Bordet, Simone" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 04, 2002 2:43 PM Subject: RE: [JBoss-dev] bin/privatekeys & bin/BeanCacheMonitor*.jar Hi Jason, > Is there source anywhere in cvs directly? No, the single source file is directly inside the jar; the only presence in CVS is the jar itself, that's the reason why they might be very old: they are not built. It was a simple example of how it is possible to monitor the bean cache, still useful IMHO if JBoss will provide the monitoring capability of the server. Juha was working on a nice gui for monitoring, the admin package under contrib if I remember well... > Do they belong in > bin/ or in > client/? Well, under client/ I normally think of jars required by client to use JBoss; I did not want the users to copy these jars in their clients, thinking that they are necessary to use JBoss :) That's why they're under bin/. Maybe a better place would be examples/monitoring/. Feel free to move them. > I was trying to clean up the release tree for the 3.0 release > (when ever > that might happen). Yes, I guessed so :) Cheers Simon _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
