Glyn To answer the technical aspects:
WSIF has two SOAP providers - one based on Axis and one based on Apache SOAP 2.2. They both support the SOAP namespace, but do it in different ways. I guess this demonstrates that technically, WSIF is reasonably independent of the particular SOAP implementation. Paul ----- Original Message ----- From: "Glyn Normington" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, April 23, 2002 9:37 AM Subject: Re: Proposed Contribution to Apache - WSIF > Sam, > > I apologise for the confusion. I was really getting at whether WSIF > includes an Axis-based SOAP provider. I agree that Paul should not comment > on Apache project structures. If Apache wants to take WSIF - and why not? - > then we need this kind of information to determine whether it should go > into Axis or somewhere else. > > >Long term, I'd love to see a WebServices project parallel to Jakarta and > >XML. > > +1. If that just involved a change to the web site to re-classify Apache > SOAP and Axis, why couldn't it be done sooner rather than later? Would > there be significant Apache project management changes as well? > > Glyn > > > > Sam > Ruby/Raleigh/IBM@ To: [EMAIL PROTECTED] > IBMUS cc: > Subject: Re: Proposed Contribution to Apache - WSIF > 22/04/02 17:00 > Please respond to > axis-dev > > > > > > Glyn Normington wrote: > > > > Assuming Apache want to take WSIF, I think it would be helpful if you > could > > briefly summarise, for the benefit of axis-dev, the relationship between > > WSIF and Axis to help decide whether WSIF should be included in Axis or > > made into a separate xml.apache.org project. > > I had suggested that Paul NOT do this. I have seen too many proposals get > mired up in discussions because the person who made the submission > expressed an opinion about the project structure before being perceived as > a part of the team. > > Long term, I'd love to see a WebServices project parallel to Jakarta and > XML. > > - Sam Ruby > > > > >
