The bundle is part of the The Knopflerfish Axis 1 package.
Implementation of a "remote" OSGi framework, using SOAP. This implementaiton does currently not support forwarding of log event from the server framework to the client. For usage instructions see Remote Framework, but replace references to ksoap-osgi with axis-osgi and ksoap_remotefw with soap_remotefw. Two xargs-file fragments that can be used when starting a server / client framework using the Axis 1 baser SOAP Remote Framework are provided by the links in this sentence.
The soap_remotefw bundle can export the entire OSGi framework as a SOAP service, by registering an instance of org.knopflerfish.service.soap.remotefw.RemoteFW into the framework, with the property SOAP.service.name = OSGiFramework
This will make the axis-osgi bundle pick up the service and export all methods. A SOAP client on another host can then access the server framework.
Typically, this "raw" SOAP service will be available on
http://and can be viewed directly with the soap_desktop browser.host :port /axis/service/OSGiFramework
The default behavior of soap_remotefw is to register a RemoteFW instance.
The soap_remotefw bundle can also run as a client and import a remote framework. In that case, a service of class
org.knopflerfish.service.remotefw.RemoteFrameworkwill be registered into the framework. Another bundle can then get this RemoteFramework service and call its "connect" method. This methods will return a BundleContext representing the remote framework. See javadocs for RemoteFramework for details.
The default behavior of soap_remotefw is to register a RemoteFramework instance.
The Swing desktop is capable of using the RemoteFramework service. If the soap_remotefw is active, the desktop will display a connection dialog allowing the user to connect to a named remote framework.