Dug, WSIF isn't trying to compete with Axis. It is at a higher level where the premise is "web services are described by WSDL and may be accessed via any protocol". It is my understanding Axis has the premise "the web service is accessed via the SOAP (protocol)".
Of course WSIF relies on Axis when the protocol is SOAP. So you're right, when the access protocol is SOAP there is nothing you can do with WSIF that you can't do with Axis alone (now that there is a DII in Axis). Where an application (eg middleware) needs to invoke a web service described by WSDL which isn't accessed via SOAP (and btw it only found out which protocol was needed at runtime), WSIF is the answer ... as long as the protocol is supported by WSIF :-) Jeremy ----- Original Message ----- From: "Doug Davis" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 02, 2002 5:15 PM Subject: Re: WSIF - Is it dead? I'd be interested in knowing what you can do with WSIF that you can't do with Axis - w.r.t. SOAP I haven't seen anything. -Dug easter <[EMAIL PROTECTED]> on 12/02/2002 11:52:00 AM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: WSIF - Is it dead? Actually that's what I started off with, till I realised it's limitations. I wouldn't mind seeing some of the WSIF stuff integrated into the axis code base.... WH Doug Davis wrote: > > > > >WH wrote: > > >>The current axis implementation is limited to working with hard coded >>web services at the source code level (unless you do some >>awesome code gymnastics), wsif provides a way to generically invoke web >>services at runtime. >> >> > >You obviously haven't used the DII interfaces in Axis. >-Dug > > > > >
