On Thursday 12 April 2007 23:13, Steven E. Harris wrote: > Niclas Hedhman <[EMAIL PROTECTED]> writes: > > Well, I think you can. You just move the 'intelligence' from the > > management client to the management bundle which is present on the > > target platform. > > By that I take it you mean that the client hands the URL over to a > specific bundle that knows how to interpret the URL as something OSGi > specific, right?
Actually not. The URL could be just a http:// ref to a bundle, but what to do with that is OSGi specific, and hence part of the code executing in the target. You said you don't want any OSGi specific stuff in your protocol. So, take JMX over RMI for instance. An MBean exposes a method void install( URL content ) throws InstallationException; For the OSGi implementation that needs to download (cache?) the content and call the BundleContext.install(). In a Tomcat equivalent, the WAR file need to be downloaded (cached?) and installed thru its mechanisms, and so on. The client and protocol is unaware of what the URL actually points to and doesn't need to know. Cheers Niclas _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
