Re: Transport jars as OSGi bundles
Glen Daniels <[email protected]>
| Newsgroups | gmane.text.xml.axis.devel,gmane.text.xml.commons.devel,gmane.comp.java.ofbiz.devel |
|---|---|
| Message-ID | <[email protected]> |
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] >