I'd have to agree with the view that Axis2/Java & Axis2/C have quite a lot in common. The sames concepts & architecture are used by both these projects. In effect, a person who understands the concepts & architecture of one, can easily understand the other. So, IMHO, we should not separate these projects. Axis2/C is a very useful project since it makes it possible to make use of it to build Web service frameworks in other languages like PHP, Ruby, Perl, C++ etc. So it has a wide are of usage, and caters to a wider audience. Hence it is not correct to even imply that it is less important. I'm sure that the Axis2/C developers & users would have taken great offense in such statements.
I've been observing this thread for sometime now, and I feel that making Axis2 a TLP is going to give rise to more problems than finding solutions to the problems at hand. What we should do is to come up with a plan to address the issues & concerns, rather than saying 'making Axis2 a TLP will solve all the problems'. Thanks Azeez On Fri, Oct 31, 2008 at 3:28 PM, Samisa Abeysinghe < [EMAIL PROTECTED]> wrote: > 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. >> > What is the last time you tested interop with Axis2/C??? > > About >> the architecture: Might be, but that doesn't mean, that it is a single >> community in practice. >> >> > > I am part of Axis2/Java and Axis2/C and you are now trying to leave me out > of that. > >> To convince me, you should give me *more* examples like the following, >> where work actually shared: >> >> > > Why should I convince you? Have you made the decision already. Rather I > guess you should convince me, given I am the one who started Axis2/C and you > are now trying to undo that. > >> >> >> >>> 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. >> >> > > We are not a minority, we are part of WS. There are not majority or > minority in WS PMC. PMCs are PMCs. I am one and I have equal rights. > > My question was, I am already a WS commiter, not an Axis2/Java or Axis2/C > comitter. What happens to me when Axis2 is made a TLP dropping C? > > Samisa... > >> >> Jochen >> >> >> > > > -- > Samisa Abeysinghe > > http://people.apache.org/~samisa/ <http://people.apache.org/%7Esamisa/> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Afkham Azeez Blog: http://afkham.org Developer Portal: http://www.wso2.org WSAS Blog: http://wso2wsas.blogspot.com Company: http://wso2.com GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760
