axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera" <>
Subject Re: Releasing transports 1.0 - dependency resolutions
Date Tue, 31 Mar 2009 05:53:34 GMT
Jarek Gawor wrote:
> On Tue, Mar 31, 2009 at 12:22 AM, Asankha C. Perera <> wrote:
>>>> 2) Move the base, local, tcp, and http transport modules back to Axis2
>>>> and release them with Axis2. That way the transports project would
>>>> only have the 'optional' transport modules and we wouldn't have to
>>>> release the transports for/with Axis2.
>> You can take back just http and local into Axis2 if that makes the release
>> possible, but not base. AFAIK the base had no relationship with the Axis2
>> http transport. I do not think the tcp transport has much value to vanilla
>> Axis2 either..
> Transport base has lots of dependencies on Axis2 and transport http
> has dependencies on transport base (and Axis2). So transport base has
> to move if we decide to move it. 
No, only the following two classes are using a two utility classes, 
which can be fixed easily. Like I said, the base will remain in the 
transports module - whether it be under commons or back again in Synapse.


> I mentioned tcp and local transport modules because they are currently enabled in Axis2
conf.xml file so
> we would need to update the configuration at least.
thats fine


Asankha C. Perera

View raw message