Hi, I've never liked JMX in that I had to open up my firewall; I would like a pluggable transport architecture built in to declarative services... For example, you would simply have a new keyword: "exposed"... In your OSGI-INF/dot.xml file or in your dot.bnd file for the Service-Component, in addition to words like "optional", you could have "exposed"... For the "provides" entry, you are telling the framework that your service is available across transport; For the "reference", you are telling "distributed declarative services" that you would like to get the service across the transport; I'm looking to auto-generate "stubs" (anyone who knows corba or rmi gets what I mean by the word "stub"); There are a number of ways to do this; This should ride a pluggable transport; Same with "remote management" -- A better way would be to have an "mxbean like" management api, that would ride "distributed declarative services" which would ride the pluggable transport; One day we might have a java that really works, a la OSGi and some "dreaming on top", like 'deployable source bundles', that is lightweight, value add (I'd like to see the system bundle decoratable, particularly at the point of "installBundle()" ), and works in the enterprise or the desktop, with a virtual and seamless development environment (and ditch this maven nightmare -- back to deployable source bundles), as opposed to this mount Everest J2EE nonsense... Back to your local station...
________________________________ From: [email protected] on behalf of Tom Kesling Sent: Tue 2/2/2010 1:54 PM To: [email protected] Subject: [osgi-dev] How to implement Remote Management via messaging I'm looking for a way to remotely manage osgi environments via messaging. Basically, I want to have multiple osgi nodes connected to our messaging infrastructure and have the ability to send commands to all of them. I'd like to know if anyone has any tips on where to start. Is there an existing implementation that I can take advatage of or should I be rolling my own. Any tips are appreciated. Thanks, osgi nube _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
<<winmail.dat>>
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
