Hi All,
We are discussing the possibility of ${subject} using OSGi. Please refer to
[1].
We would really appreciate your take on this and use case that come up
with.
Summary:
1. Being able to deploy aar/mar as OSGi bundles.
2. This wouldn't break the backward compatibility.
3. axis2-kernel doesn't depend on OSGi classes but manifest.mf file will
have extra OSGi headers
4. There is a tight dependency between axis2 services and modules that
needed to be lax in order to provide OSGi support. ex: if service A depends
on module B, if module B is not available at the time of service A loaded,
then service A will be put to "unresolved" list. When the module B is
available, service "A" will be removed from "unresolved" list.
5. Being able deploy other files as OSGi bundles and pick up by axis2
deployment as web services.
Thank you!
Saminda
Reference:
[1]. http://marc.info/?l=axis-dev&m=121328806827717&w=2
--
Saminda Abeyruwan
Senior Software Engineer
WSO2 Inc. - www.wso2.org
