Hi Baham, WSIF is an API for invoking Web Services.
What sets WSIF apart from other Web Service API's is that it provides binding independent access to any Web Service and has an API that closely matches WSDL rather than the API of the underlying protocol or transport package. WSIF uses a 'provider' to implement the logic required for a particular WSDL binding, and WSIF provider's are pluggable at run time, transparently to WSIF client programs. WSIF comes with providers that implement the standard WSDL soap binding, one based on Apache SOAP and another based on Apache AXIS, and it also comes with providers that implement new WSDL bindings for things like Java, EJB, and JMS. What these providers do is allow you to describe a local Java class, or an EJB, or a JMS application with WSDL the same way you would describe a SOAP service with WSDL. A WSIF client program can then run unchanged and access any of the services described by the new WSDL bindings. Which provider WSIF will use and therefore which service is accessed can be set to a default, or decided on at run time, controlled by the environment or the client program itself. The WSIF provider architecture allows anyone to write a provider that implements a new WSDL binding, and have that provider discovered at run time by WSIF and usable by any client program using the WSIF API, again without requiring any client code changes. This has several benefits for applications not least being the ease with which you can migrate from say Apache SOAP 2.3 to Apache AXIS, or any other future SOAP API . You can find out more about WSIF at http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-axis-wsif/java/readme.htm ...ant Anthony Elder [EMAIL PROTECTED] Web Services Development IBM UK Laboratories, Hursley Park (+44) 01962 818320, x248320, MP208. "Bahman Kalali" <[EMAIL PROTECTED]> on 29/11/2002 19:45:43 Please respond to [EMAIL PROTECTED] To: <[EMAIL PROTECTED]> cc: Subject: Re: WSIF - Is it dead? I have been working on WSDL for long time but I have never used WSIF. Can anyone tell me what is WSIF? and what is the relation between WSDL and WSIF? Thank you very much in advance for your advice, --Bahman ----- Original Message ----- From: "Pae Choi" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 29, 2002 5:41 PM Subject: Re: WSIF - Is it dead? > That's a strong viewpoint from an IBMer. Maybe that's because > the package came from IBM, perhaps? > > I can count you as one user, but not buying the expression "Lots." > > Any comments? So I can increase the counter, two, three, ... :-) > > > pae > > > ----- Original Message ----- > From: "Anthony Elder" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, November 29, 2002 12:27 PM > Subject: Re: WSIF - Is it dead? > > > > > > No WSIF isn't dead! Lots of people are using it. > > > > Probably the biggest most recent example is the quite high profile it took > > in the announcement of IBM's latest version of WebSphere this week, see: > > > http://www.aspnews.com/strategies/companies/article/0,2350,10576_1547561,00 . > html > > > http://www.ibm.com/software/info1/websphere/index.jsp?tab=news/ibmnews/pr112 > 502&S_TACT=102BBW01&S_CMP=campaign > > > > I think one of the reasons WSIF doesn't get many questions on the AXIS > > lists is that people still seem to use the old alphaWorks discussion group > > (http://www.alphaworks.ibm.com/forum/wsif.nsf) for questions. I've asked > > alphaWorks to update the WSIF page to point to Apache but it hasn't happen > > yet. > > > > I encourage you to keep on using it, as far as I know there is nothing > else > > available that has similar functionality. > > > > ...ant > > > > Anthony Elder > > [EMAIL PROTECTED] > > Web Services Development > > IBM UK Laboratories, Hursley Park > > (+44) 01962 818320, x248320, MP208. > > > > > > easter <[EMAIL PROTECTED]> on 29/11/2002 16:26:42 > > > > Please respond to [EMAIL PROTECTED] > > > > To: [EMAIL PROTECTED] > > cc: > > Subject: WSIF - Is it dead? > > > > > > > > I've noticed since my subscription to this list, that no-one at all > > seems to use WSIF, or (less likely) it's too well documented and > > bug-free to warrant any > > mailing list discussions. > > > > Is there something else I should be using instead? Is it going to go away? > > > > I've found nothing else which allows me to generically and dynamically > > connect 2 web services together using nothing > > more than their WSDL descriptions. > > I feel since I seem to be the only one on the planet to do this, perhaps > > I'm doing something wrong? > > > > Cheers. > > WH > > > > > > > > >
