synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Davanum Srinivas <>
Subject Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Date Tue, 22 Apr 2008 20:47:41 GMT
Hash: SHA1

Cool. I'll cleanup whatever stale transports are in Axis2.


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:
Version: GnuPG v1.4.5 (Cygwin)


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

View raw message