On Fri, 2008-10-31 at 09:37 +0100, Jochen Wiedmann wrote: > On Fri, Oct 31, 2008 at 9:21 AM, Samisa Abeysinghe > <[EMAIL PROTECTED]> wrote: > > > -1. They share the same architecture. They do the same this, only the > > implementation is different. > > And they are supposed to work with each other, interop in other words, so > > they have lot in common. > > Interoperability is not an argument. Axis is trying hard to be > interoperable with others as well. About > the architecture: Might be, but that doesn't mean, that it is a single > community in practice. > > To convince me, you should give me *more* examples like the following, > where work actually shared: > > > > It is a fact that, you can interop being disjoint projects. However, we even > > use the WSDL2Code tool to generate code. If Axis2/Java becomes a separate > > TLP and can an Axis2/C comittor do changed to that tool? > > What's the problem? I can't see anyone from preventing an Axis2/C > committer being a > Axis2/Java committer as well, if he or she is interested in it? My > expectation would be, > though, that it is a minority only, who wants it.
You may not want it. But it is being deployed in various production systems. Those people want it. And a common deployment scenario is using Axis2/Java in server side and Axis2/C in client side. Actually we have seen same people asking questions in both Axis2/Java and Axis2/C user lists. Again many people are using WSDL2C tool. In order to do update this tool a developer should have a good understanding on Axis2/C and Axis2/Java. If we make Axis2 a TLP and keep Axis2/C as it is then enhancement of this tool may stop. The other thing is Axis2/C and Axis2/Java are not competitors. Axis2/Java helped to build Axis2/C and also it's community. So making Axis2/Java a TLP will affect Axis2/C user community. -Manjula. > > > Jochen > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
