Glen/Andreas, Sorry for the delay in responding to this ....
You are correct Glen, and the axis2-kernel is the bundle which loads the transports and these transport bundles can be made available to the axis2 bundle in one of many ways, (transport bundles as fragments of the axis2 fragment host bundle in which case transport bundles will not have its own classloader rather they will use the classloader of the host bundle, using the Dynamic-Imports feature on axis2 bundle, using the boot delegation and so on). For the moment we are using the Dynamic-Imports and I guess fragments are the cleaner way of doing this..... After these transport classes are loaded by the axis2 bundle it is just it who is going to use it and we do not need to export the transports and the classloader will be able to find the transports. Thanks, Ruwan On Fri, Oct 10, 2008 at 10:16 PM, Glen Daniels <[EMAIL PROTECTED]>wrote: > Hi Andreas: > > We've already got some capability to deploy transport jars in > repository/transports/, so can't we just do the same thing we do for service > or module bundles? We just need to make sure that accesses to the transport > classes are via the correct classloaders. Am I missing anything tricky? > > --Glen > > > Andreas Veithen wrote: > >> A short question I always wanted to ask about OSGi and Axis2: At runtime >> every bundle gets its own classloader. On the other hand, the classical way >> to load transports in Axis2 is by declaring them (with their class names) in >> axis2.xml. Since the transport implementation lives in its own classloader, >> you can't do this in an OSGi environment. How will the transports be loaded >> in that case? >> >> Andreas >> >> On 7 oct. 08, at 03:18, Ruwan Linton wrote: >> >> Hi devs, >>> >>> I would like to propose the transport jar artifacts to be OSGi bundles, >>> because synapse artifacts are OSGi bundles so that in an OSGi container >>> we >>> should be able to use these transport jar artifacts as OSGi bundles >>> effectively. >>> >>> I would like to do this... since I did the same for synapse artifacts. >>> Making these artifacts OSGi bundles doesn't affect the normal existing >>> non >>> OSGi operation of the jar artifacts. Basically we will be having a jar >>> artifact with some more information on the MANIFEST ... >>> >>> Thanks, >>> Ruwan >>> >>> -- >>> Ruwan Linton >>> http://wso2.org - "Oxygenating the Web Services Platform" >>> http://ruwansblog.blogspot.com/ >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> -- Ruwan Linton http://wso2.org - "Oxygenating the Web Services Platform" http://ruwansblog.blogspot.com/
