Costin Manolache wrote:
I think the client part should just use JRMP to talk to MX4J (or one of the others it provides).Craig R. McClanahan wrote:I like using the custom Ant tasks included with Tomcat 4.1 for manipulation via manager, so that I can create a "reload" target. If you don't use Ant, it's just as easy to leave a browser window open to:I don't know if you looked at the JMX ant tasks in modeler. If we add some "simple remote JMX" feature in Manager - and implement the client side in the modeler ant tasks - it should be possible to control every aspect of tomcat from ant.
Ok, I'm being lazy here; I just don't feel like inventing our own custom protocol when one already exists ;-)
Remy
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>