I tried Axis2 1.5 RC1 one or two weeks ago and have a patch for the 2.x
stream. The changes should be mostly applicable for 1.x. Maybe you can open
a JIRA for the effort and I will attach the patch.
Thanks,
Raymond
--------------------------------------------------
From: "Simon Laws" <[email protected]>
Sent: Tuesday, May 05, 2009 5:01 AM
To: <[email protected]>; <[email protected]>
Subject: Re: [1.x] How about releasing 1.5 ?
On Tue, May 5, 2009 at 12:53 PM, ant elder <[email protected]> wrote:
On Mon, Apr 20, 2009 at 8:52 PM, ant elder <[email protected]> wrote:
The Axis2 1.5 release looks like it could start being voted on this week
but that often can take some time and then the JMS transport would be
released separately after that and then we'd need some time to polish a
Tuscany release including those. So all that would likley take some
weeks.
There are alternatives like trying to port the new JMS transport to our
existing ws binding, but thats likely a bit more work.
If we're to get a 1.5 release out this month I'm starting to think we
should go with porting the new Axis2 JMS transport to work with the
existing Tuscany WS binding.
Axis2 still haven't had their release and after that does happen there
would need to be a follow on release of the transports and all that
will have to take at lease a couple of weeks and then we'd need to
pick it up in Tuscany before doing the Tuscany 1.5 release...so all
that would likely push the Tuscany release in to June.
So unless anyone can see any issues with the approach I'm going to
start looking at bringing the new Axis2 JMS transport into the Tuscany
WS binding. At least that will help us know how hard it is to do and
we can throw it all away if the Axis2 releases do start to happen more
quickly.
...ant
Sounds like the right thing to do given where we are. We also have
this WSDL issue that Dave raised that I was going to look at. Is it
safe to assume that we wait until these are done before retaking the
branch?
Simon
