JMX remoting (as it stands now) is in pretty decent shape. By this I mean the main features have been implemented (detectors, connectors, classloading, etc.). However, it has not been strenuously tested in the field yet.
Also, much of what is there now will probably change to use the more generic invoker framework in the near future. The same functionality will still be there, but much of the remoting code will be moved into the invoker framework code. To be specific about your classloader question, the current code will ignore classloading feature if can find class locally. Will remotely load the class if can not find locally. All this is working now. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > Anatoly Akkerman > Sent: Tuesday, February 18, 2003 5:57 PM > To: JBoss-Dev > Subject: [JBoss-dev] jmx remoting + copyright in a jbossmx file > > > Hi, > > I've been browsing the HEAD in CVS to find out what the status of JMX > remoting is. It appears that significant pieces have been > implemented. I > was hoping to use some of this stuff decoupled from JBoss > itself, is it > usable already? (I understand that classloading is a work in > progress, > can this work if all classes are available in both MBean servers?) > > ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
