23 lines
1.2 KiB
HTML
23 lines
1.2 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Use WSIF with Web services that offer multiple bindings</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h5><A NAME="wswsifbnd">Use WSIF with Web services that offer multiple bindings</A></h5>
|
||
|
|
|
||
|
|
<p>You can use WSIF to enable client applications to switch between service bindings at run time, to enable them to use the optimum binding, and to call operations on a Web service provider.</p>
|
||
|
|
|
||
|
|
<p>For example, a Web service provider can offer a SOAP binding for the service and a local Java binding that allows you to treat the local service implementation (a Java class) as a Web service. If the client is deployed in the same environment as the service, the local Java binding for the service can be used and provides more efficient communication with the service by making direct Java calls rather than using the SOAP binding.</p>
|
||
|
|
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|