axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glen Daniels <>
Subject Re: Releasing transports 1.0 - dependency resolutions
Date Tue, 31 Mar 2009 20:02:59 GMT
Hi Jarek, all:

Jarek Gawor wrote:
> So sounds like we agree on moving the http module back to Axis2 and
> leaving transport base where it is (after fixing the utility classes
> dependency). What about tcp and local? Should we move it or leave it
> where it is? Do Axis2 users expect local and/or tcp transports to be
> installed by default?

If we're really thinking about doing this, local should be there IMO, both
for quick accesses (HTTP-based service gets called, say, and it calls another
service via local transport) and for testing.  TCP not so much.

So, to be clear, the point of this is to... remove the dependency from Axis2
to the other transports?  I do still want to be able to release the
transports (including HTTP) separately from the full Axis2 distributions, so
I'm not entirely sure that moving http/local back necessarily solves things.
 I'm not against it (I actually think all the transports should be under the
Axis2 TLP as a subproject, but that's another conversation :)), I'm just not
sure it entirely helps with this problem long term.

Once we have a stable Axis2 1.5 base for the transports to depend on, this
problem should go away until the next time we have a core change.  So if it's
possible, I'm still thinking about the "release 1.5 jars then depend on those
for the transport releases" option....

Also, I'd really like to get 1.5 out the door ASAP, it's lingered way too
long already.  So whatever solution gets us there soonest with consensus is
the one I'll be happy with.


View raw message