synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <>
Subject Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Date Tue, 22 Apr 2008 22:09:33 GMT
I would propose to leave the transports in Synapse but to have a  
distinct Maven module for each protocol, with the minimal set of  
dependencies required for that protocol implementation. This would  
allow Axis2 users to include these transport easily in their Maven  
builds. It would also be interesting to Synapse users: As an example,  
I have a project where I package Synapse together with the relevant  
config files into a WAR. With Synapse 1.1.1, the WAR takes 24MB, with  
the latest snapshots, 32MB. The dependencies for the FIX protocol  
(which I will never use) alone take more than 4MB. Having different  
Maven modules for the various transports would allow better control of  
what is included in the packaging.


On 22 Apr 2008, at 22:41, Asankha C. Perera wrote:

> Davanum Srinivas wrote:
>> Agreed that this is definitely a problem.
>> Next question, is do you want do this in Synapse Commons (do you  
>> have one?) or WS Commons?
> We already have all the transports in a separate Maven module, which  
> is published to Apache snapshots and Central repo.. As far as I am  
> concerned,
> there is no requirement to re-package this code and ship it  
> elsewhere.. If a user wants a particular transport as a separate  
> module, they can ask for an enhancement for it, and we will do our  
> best to facilitate it.
> So if we are going to have a vote on this 'topic' on axis-dev, I am  
> +1 to deleting the stale copies of the transports currently in Axis2.
> But if you are going to call for a vote on dev@synapse.a.o to remove  
> critical code developed by the Synapse community from our SVN, to  
> make it easier for axis2 users to "get" these transports, I'm  
> definitely -1
> asankha
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message