I'd been doing some playing with JMX too. I was mostly just interested in exposing a function that returns a map, eg: #(@deref counters), as a JMX bean that exposed properties representing the fields in the map.
I'm not very experienced with JMX, but I got the impression that it would probably be better to use OpenMBeans (which are a subtype of DynamicMBeans), rather than use straight dynamic-mbeans, because the openmbeans use standardized classes for passing the data, so you dont have to worry about classloader issues, and the clojure data structures being available to the jmx client. It seems that OpenMBeans are pretty similar to MXBeans, but are dynamic. Does it make sense to have the jmx server be changed to expose OpenMBeans? This would require the server code to expose clojure lists and maps and stuff as opentypes. -- Dave --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
