RE: What is the current status of WSIF

When building the WSIF client for Websphere, remember to use WSIF 2.0 not the IBM one, and use this:

WSIFPluggableProviders.overrideDefaultProvider("http://schemas.xmlsoap.org/wsdl/soap/",  new WSIFDynamicProvider_ApacheAxis());

IBM WSIF doesn't provide this WSIFDynamicProvider_ApacheAxis() .

Sandip

 

---

From: "Todd Eisemann" <Todd.Eisemannchordiant.com>
Reply-To: wsif-userws.apache.org
To: <wsif-userws.apache.org>
Subject: RE: What is the current status of WSIF
Date: Tue, 12 Jun 2007 14:56:27 -0700

Hello Doug

 

I am using WAS 6.1.0.5&nbsp;  (and I think we even had the problems on earlier release of WAS, such as was 6.0)

 

In the was runtime jar (in the plugin directoy), you will find all of the WSIF classes – with different implementation than WSIF 2.0

 

The IBM implementation of WSIFServiceImpl.getPort() is really slow – especially the protected method setupTypeMappings() is horrendous, especially, when you have a WSDL that has lots of XSD data types defined.  

 

Hope that helps

 

---

From: Jackson, Douglas [mailto:djackso2ugs.com]
Sent: Tuesday, June 12, 2007 1:33 PM
To: wsif-userws.apache.org
Subject: RE: What is the current status of WSIF

 

Hi!

We are using WSIF on Websphere, and are not aware of any problems – can you

elaborate on which version you are seeing these problems?

-Doug.

 

---

From: Todd Eisemann [mailto:Todd.Eisemannchordiant.com]
Sent: Tuesday, June 12, 2007 12:11 PM
To: wsif-userws.apache.org
Subject: RE: What is the current status of WSIF

 

HI all

 

Just a quick opinion.

We have been using WSIF for some web service and lots of POJO bound invocations. It works well… Things have gone pretty well. ;  I’d love to see WSIF move up to a newer WSDL4J parser.

 

He have found a few thread sync problems in WSIF and have been able to work around those.

 

HOWEVER, we have found that IBM WebSphere runtime jar ALSO includes a very different version of WSIF. The IBM version has horrible performance and lots of thread synchronization problems. This has caused us no end of pain.  In WebSphere, you cannot work the class path to use Apache WSIF.

 

Therefore, if you plan to use WSIF in WebSphere, I believe you will have problems. However, if you use it anywhere else, I believe you will find it to be a pleasant experience.

Thanks

 

---

From: sambit kumar dikshit [mailto:sambit.dikshitapple.com]
Sent: Tuesday, June 12, 2007 9:57 AM
To: wsif-userws.apache.org
Subject: Re: What is the current status of WSIF

 

Hi Ahmet,

   I could see the future is bright. We have been using it for a while and successfully built a service invocation framework using WSIF and extending some of the features. It is a really good stuff where you want to invoke various types of services running on different protocol e.g http, soap, jms, POJO, EJB etc. 

 

Regards

-Sambit&nbsp; 

On Jun 12, 2007, at 7:40 AM, Ahmet Emre wrote:

 

We are starting to use some web services first time in our company.  There were few web service calls we had developed in the past and we were using WSIF. Now we do expect more and more web service calls being made and we do expect web services becoming an important part of the architecture in a year or so.

How do you guys see WSIF in the future? In order to invoke Web Services do you believe WSIF is the way to go? Or would you say WSIF is legacy and focus on something else? As I researched little bit, WSIF community is not very active anymore. There are many other things going on and it looks like Service Component Artchitecture (SCA) and some Eclipse Web Tools Platform (WTP) are the ones to consider first.

Thanks for sharing your experience and thoughts on this subject.

 

The information transmitted herewith is sensitive information of Chordiant Software or its customers and is intended only for use to the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon, this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.

The information transmitted herewith is sensitive information of Chordiant Software or its customers and is intended only for use to the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon, this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.