On Sun, Nov 7, 2010 at 7:14 AM, Dennis Sosnoski <d...@sosnoski.com> wrote: > > > I do realize that WSO2 has built its whole operation around the > commercialization of the Axis2 stack and related technologies, and as > founder and chairman of WSO2 you may rightly feel that negative publicity > for Axis2 hurts your company. But I don't think that gives you the right to > effectively accuse me of some sort of personal vendetta against the project. >
Dennis, I've been a contributor to Apache for 10+ years. My comments on this list are not about my work - you can try to twist it and say that it is because I have a commercial interest in Axis2 but you'd be sooooo wrong. See: http://www.google.lk/search?q=axis2+%2Bsite:wso2.com As you can see there's little mention of Axis2 in the entire wso2.com site- yes all of our stuff uses Axis2 in its heart but that's for the most part internal. WSO2 is not built on commercialization of the Axis2 stack. If you use Data Services, Mash Server, ESB, BAM, Governance Registry, Identity Server etc. you'll see no Axis2 at all. That's an internal library we care a lot about because of the power and flexibility Axis2 has. (Try 100% capability to stream for one.) We of course care about it in the Application Server (which hosts services) but honestly even in that Axis2 AARs/JAX-WS is just one class of services we host. If we're hosting JAX-WS we could use CXF underneath even and you wouldn't notice - and if there was customer demand we'd do that without any hesitation; we're not religious about library you use to write your little Web service. Not one has asked for it. You can do bad publicity about Axis2 and it will not bother me with my WSO2 hat on. With my ASF hat on I am very disappointed when I see such bad PR and I wish such was not the case. I unfortunately don't have the time to fix code myself and am doing what I can to get others to contribute towards improving it. In your case you apparently believe there's nothing about Axis2 that's special and better vs. CXF or Metro or something else. That's fine too dude :). The reality is the "is my ws-* stack faster than yours" game is over - and no one other than you seems to care about it that much! There are cases when Axis2 is fastest, and others where Metro is fastest and others where CXF is fastest. That comes from various design decisions taken by the various engines at various times. Some of it is due to bad code that could be improved. Design decisions are made for reasons that were apparent at the time - some of those may be considered wrong later. However nothing is absolute in the world of design. IMO WS-* stacks are like XML parsers now - they need to be fast and scalable and reliable. Axis2 family is. You may not agree but hundreds of thousands of people agree. I'm sure CXF is too as must be Metro. It comes down to developer choice. If you want to help the world then find ways to improve interoperability between various WS-* engines to get every case to the point of "it just works". Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Director & Chief Scientist; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman & CEO; WSO2; http://wso2.com/ Founder & Director; Thinkcube Systems; http://www.thinkcube.com/ Member; Apache Software Foundation; http://www.apache.org/ Member; Sahana Software Foundation; http://www.sahanafoundation.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ Blog: http://sanjiva.weerawarana.org/
