The OSGi metadata for the axis2-osgi uber-JAR and the individual JARs were created by different people at different times. I would not expect that they play nicely together. Anyway, if you can come up with a maven-bundle-plugin configuration that works and that is somewhat self-maintaining (i.e. without hardcoded Import-Package and Export-Package attributes), I'll be happy to add that to the build.
Andreas On Fri, Mar 4, 2011 at 02:08, Ivan <[email protected]> wrote: > Not sure I understand you correctly. > From my side, axis2-osgi is not only an uber-bundle, it seems to also > support to discovery other sub-modules (e.g. addressing). And in AXIS2-4311, > it describes that there are split-package issues in some of those packages, > and now axis2-osgi have solved it by including all those related components > in one bundle, so at least, axis2-osgi is one way to solve the split-package > issue ( Not sure whether it is possible to rename those duplicate packages). > While in AXIS2-4787, it is reported that some configurations of the bundle > are out-of-date, and the final solution is to remove those configurations > temporarily. The problem is that some of the components (e.g. axis2-jaxws) > are not included in the axis2-osgi, so it seems to me there is no way to use > those components directly in OSGi environment. > That is why I hope to recover the removed maven-bundle-plugin configurations > with default settings, and think those guys who really uses axis2 in OSGi > environment would report issues for incorrect bundle configuration :-) > I am trying to enable AXIS2 in Geronimo, and I hope to use the native Aixs2 > bundles directly (the more, the better) > Thanks. > > 2011/3/4 Andreas Veithen <[email protected]> >> >> These three things have nothing to do with each other, except that >> AXIS2-4311 blocks AXIS2-4787. axis2-osgi is an "uber-bundle" that >> packages multiple Axis2 JARs into a single OSGi bundle. On the other >> hand, AXIS2-4311 and AXIS2-4787 describe problems when trying to use >> the Axis2 JARs as individual OSGi bundles. >> >> Andreas >> >> On Thu, Mar 3, 2011 at 09:12, Ivan <[email protected]> wrote: >> > Since the axis2-osgi somewhat solves the split packages issue mentioned >> > in >> > AXIS2-4311, how about recovering the removed OSGi configurations in >> > AXIS2-4787 ? >> > Thanks. >> > >> > 2011/3/3 Ivan <[email protected]> >> >> >> >> Hi, I am trying to use axis2-osgi-1.5.4 bundle in OSGi environment, and >> >> the bundle is failed to resovle due to an import package >> >> javax.jms;version="1.1". I searched the codes packaged in that jar >> >> file, and >> >> did not find any use of classes in that package. >> >> So, why is javax.jms is added in the imported list, do I miss anything >> >> ? >> >> Thanks. >> >> >> >> -- >> >> Ivan >> > >> > >> > >> > -- >> > Ivan >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > Ivan > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
