Hi Brindy, 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?
Yes it is. This is the second phase of OSGi/Axis2 integration. During the first phase of OSGi integration we wanted to properly bundle Axis2. Hence we came up with org.apache.axis2.osgi.jar bundle. You will be able to test this bundle from the instruction available in https://svn.apache.org/repos/asf/webservices/axis2/scratch/java/saminda/osgi_test. Follow axis2_osgi_integration.pdf to run and test the bundle. As you have mentioned, org.apache.axis2.osgi.jar bundle contains/export Axis2 related packages and other packages needed to be imported. Second phase of Axis2/OSGi integration is to consume OSGi SOA infrastructure to expose an OSGi service as a Web service. As you have mentioned, our goal is to use Directory object to fill the meta-date needed for the OSGi service and create Axis2 Web service out of it. We are in the process of mapping services.xml to a bunch of name/value pairs that needed for Directory object and use the special key "org.apache.axis2.ws" to distinguish the OSGi service that needed to be expose as web service. Please be kind elaborate on #3. IMO it wasn't in our original plan. We wanted to get OSGi/Axis2 integration complete before next Axis2 major release (1.5). Thank you! Saminda > > > > -- > 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] > > This gives the following advantages:
