ws-kandula-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Amila Suriarachchi <amilasuriarach...@gmail.com>
Subject Re: Split packages issue (AXIS2-4311)
Date Tue, 25 May 2010 11:52:19 GMT
On Sun, May 23, 2010 at 5:21 PM, Andreas Veithen
<andreas.veithen@gmail.com>wrote:

> On Sat, May 22, 2010 at 06:41, Amila Suriarachchi
> <amilasuriarachchi@gmail.com> wrote:
> >
> >
> > On Fri, May 21, 2010 at 12:43 AM, Andreas Veithen
> > <andreas.veithen@gmail.com> 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?
> >
> > I agree with you that there are some areas we need to re factor  and
> find
> > the proper way of doing it.
> >
> > We did the Axis2 1.5 release last year May but actually cut the branch on
> > December as I remember. So my idea was to do an Axis2 1.6 release with
> > whatever the fixes we have done after cut the 1.5 branch. Otherwise
> people
> > tend to think Axis2 has died.
> >
> > The split package problem is actually part of the whole Axis2 OSGI work.
> > Saminda started this discussion some time ago and there was no progress
> > after that.
> >
> > So my suggestion is to just wait until Axiom and woden releases (which I
> > believe happen shortly) and cut the Axis2 1.6 branch. Then we can take
> the
> > topics like "Axis2 OSGI" , "Axis2 Spring integration" and do subsequent
> > releases with them.
> >
> > And also I think synapse people wait on Axis2 1.6 release. So lets do
> Axis2
> > 1.6 with whatever fixes we can do with and target major changes to Axis2
> > 1.7.
>
> I tend to agree with that from a purely Axis2 point of view. Not sure
> though what the Geronimo folks think about that, considering that 1.7
> will not be release before a long time. Don't forget that they are one
> of our important "customers"...
>

I haven't looked into the jira, when I send the reply. As I saw they have
the option of using it as a one bundle isn't it?

thanks,
Amila.


>
> > thanks,
> > Amila.
> >
> >
> >>
> >> Andreas
> >>
> >> [1] http://markmail.org/message/fgtbr6tzpfemlery
> >> [2] http://markmail.org/thread/i6cq72unknnnvjy5
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>
> >
> >
> >
> > --
> > Amila Suriarachchi
> > WSO2 Inc.
> > blog: http://amilachinthaka.blogspot.com/
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>


-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Mime
View raw message