There is a number of split packages just between the jaxws and metadata modules.
If OSGi is the primary reason for fixing these split package problems then we also have to consider how is Axis2 supposed to be deployed in the OSGi environment. That is, is it deployed as a set of individual bundles or one big bundle consisting of all (or most) modules. If one big bundle then we don't have to fix the split packages but we have to remove the OSGI metadata from individual modules to reduce confusion. If individual bundles then we pretty much have to fix the split package problems and fix/update the OSGi manifest info for each module. Jarek On Thu, May 20, 2010 at 3:13 PM, Andreas Veithen <[email protected]> wrote: > Hi devs, > > I think we should have a look at AXIS2-4311 and see if and how we can > fix that for the 1.6 release. > > I had a quick lock at the different packages and here are my > preliminary conclusions: > > * org.apache.axis2.util in axis2-adb only contains a single utility > class --> should not cause much trouble to move it elsewhere > * org.apache.axis2.transport.jms is no longer in axis2-kernel. > * org.apache.axis2.transport.http in axis2-kernel mainly contains the > standard MessageFormatter implementations. Obviously the package name > is no longer appropriate for this and it would make sense to move > these classes. However, this means that users need to change their > axis2.xml file. Note that cleaning this up would also be a good > opportunity to move the non standard message builders/formatters from > the transports project to the core Axis2 project, as discussed back in > december 2008 [1] [2]. > > Thoughts? > > Andreas > > [1] http://markmail.org/message/fgtbr6tzpfemlery > [2] http://markmail.org/thread/i6cq72unknnnvjy5 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
