Ted Neward wrote: >>... The entire JBoss server has been written as a set >>of JMX services, and you can add your own JMX MBeans to provide further >>services. Those MBeans are then portable to other servers by virtue of >>being MBeans. >> > Don't you think you're abusing the intent/Zen of the JMX Spec, doing this? > It's almost like using JNDI as a database API or JDBC as a naming > service--doable, but it sort of misses the point. :)
Yes, I agree that it's not the perfect approach. JMX, as a spec, was probably not inteded to be used like this, but until we have something better it works pretty well. It might have been more useful to have a pure service API to build the server, but since JMX fulfilled most of the goals of such an API (with the addition of custom service interfaces :-/) it is quite ok. Fair enough? /Rickard -- Rickard �berg Author of "Mastering RMI" Chief Architect, TheServerSide.com The Middleware Company - We Build Experts! =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
