rationale to use WSIF with complex types

["Volkmann, Mark" <Ma...@AGEDWARDS.com>]

If I understand WSIF correctly, if the service you want to invoke requires
complex parameters or has a complex return type then you must use some other
tool such as WSDL2Java in Axis to generate the Java service interface and
classes to represent the complex types.  Once I take that step, what's the
benefit of using WSIF?  I can just use the stub class generated by WSDL2Java
to invoke the web service which would be much faster than WSIF because it
doesn't require parsing the WSDL again at runtime.  It also requires less
code in the client to do it with the Axis stub because you don't have to
setup the type mappings in the client code.  Am I missing a benefit of using
WSIF?


***********************************************************************************
WARNING:  All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.
************************************************************************************

Re: rationale to use WSIF with complex types

[Nirmal Mukhi <nm...@us.ibm.com>]

Hello Mark,

The advantage of using WSIF (whether you use complex types or not) is the 
flexibility it offers when it comes to using a service. Since the API is 
focused on the abstract service description, it lets you switch the 
binding being used, the port being used (and in fact adapt your runtime to 
new protocols by allowing you to plug in your own binding definitions and 
supporting WSIF providers), and have your app code oblivious to all such 
changes that don't affect the core functionality offered by the service. 
The WSIF web pages have some more information. Also see a recent article: 
http://webservices.devchannel.org/article.pl?sid=03/04/22/068231&mode=thread&tid=25 
that gives a practical example of how this is useful.

Thanks,
Nirmal.




"Volkmann, Mark" <Ma...@AGEDWARDS.com>
05/22/2003 09:19 AM
Please respond to wsif-user
 
        To:     "'wsif-user@ws.apache.org'" <ws...@ws.apache.org>
        cc: 
        Subject:        rationale to use WSIF with complex types


If I understand WSIF correctly, if the service you want to invoke requires 
complex parameters or has a complex return type then you must use some 
other tool such as WSDL2Java in Axis to generate the Java service 
interface and classes to represent the complex types.  Once I take that 
step, what's the benefit of using WSIF?  I can just use the stub class 
generated by WSDL2Java to invoke the web service which would be much 
faster than WSIF because it doesn't require parsing the WSDL again at 
runtime.  It also requires less code in the client to do it with the Axis 
stub because you don't have to setup the type mappings in the client code. 
 Am I missing a benefit of using WSIF?


***********************************************************************************
WARNING: All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.
************************************************************************************