axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michele Mazzucco <>
Subject Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Date Wed, 23 Apr 2008 12:59:22 GMT

I disagree, each transport is composed by just a few classes, not  
"megs of code".
I can't see really see where the problem is if you put JMS and SMTP  
transports into the same jar file.


On 23 Apr 2008, at 13:09, Glen Daniels wrote:

> Hi Michele:
> Michele Mazzucco wrote:
>>> - First of all, Asankha, why "synapse-transports.jar"?? That  
>>> makes no sense to me- so if you have a bug in the VFS code you'll  
>>> rev all the stuff? Why? There should be one jar per transport.
>> Java provides packages for that. There's no need to have tons of  
>> jars!
> There are well-understood tradeoffs between complication and  
> flexibility here.  Having one transport per jar means, as Sanjiva  
> notes, that you can independently version and release transports.   
> It also means that I don't need to carry around megs of code which  
> is useless to me when I want just one transport.
> Forcing JMS and SMTP into one "transports.jar" seems just as weird  
> to me as putting Axiom and Neethi into one "policy-and-xml.jar". :)
> Now, that said - I do think it's fine if you want to make a  
> deployment *option* that's just one jar.  I think Axis2 might also  
> want to be making available an axis2-complete.jar (name not  
> important) that has Axis2 plus all WS dependencies in it for ease  
> of use in embedding scenarios.  But I think these are convenience  
> options that users can pick, as opposed to the right way to do  
> things in the mainstream.
> Thanks,
> --Glen
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message