Ted Neward wrote: >>Then, if you are going to make some "proprietary" developments, why not >>instead use an app server that offer what you need (hot-deployement) and >>make proprietary developments part of JMX service (that are more and more >>available in app servers)? There are some app servers that offer >>hot-deployement features. >> >> > Whoa--JMX has nothing to do with what's going on here. JMX is about managing > the server, not adding functionality to the services managed by the app > server. This is completely orthogonal.
That depends on how you use JMX. JMX can indeed be used for extending the services provided. 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. /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".
