Hi all,
I've been exchanging a view comments with Davanum who asked me to post this
here.
I like the work done so far on integrating OSGi with Axis2 but for it to be
really useful, bundles should not have to be coupled to Axis2. I believe
this is the plan anway, but just thought I should share how I think this
should work.
I want to be able to expose OSGi services as web services transparently and
without having any dependency on a web service implementation. For
instance, I might have an Activator which defines a service using the
standard OSGi approach:
public class MyActivator implements Activator {
private ServiceReference ref;
public void start(BundleContext context) {
Dictionary props = new HashTable();
props.put("webservice", "path/to/webservice/NameOfService");
ref = context.registerService(SomeInterface.class.getName(), new
ImplementationOfSomeInterface(), props);
}
public void stop(BundleContext context) {
// ...
}
}
At the point the service is registered the web service implementation should
notice that a service has been registered which has the "webservice"
property specified and make it available at the given path. When the
service is unregistered or the bundle is stopped the implementation should
be removed.
This gives the following advantages:
1) No dependency on any specific web service implementation
2) The service is available natively to other OSGi bundles
3) Other remoting mechanisms (in addition to or instead of web services,
e.g. AMF) can use the same mechanism
So I guess I am looking for confirmation this is the intention with the OSGi
part of Axis2 and what the time line is for this to be implemented?
Thanks in advance.
Cheers,
Brindy
--
View this message in context:
http://www.nabble.com/Direction-of-Axis2-%2B-OSGi-tp18982493p18982493.html
Sent from the Axis - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
