nmukhi 2002/12/30 11:01:44
Modified: java/doc faq.htm
Log:
Fixed a bit of the FAQ
Revision Changes Path
1.4 +38 -22 xml-axis-wsif/java/doc/faq.htm
Index: faq.htm
===================================================================
RCS file: /home/cvs/xml-axis-wsif/java/doc/faq.htm,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- faq.htm 25 Nov 2002 06:32:56 -0000 1.3
+++ faq.htm 30 Dec 2002 19:01:44 -0000 1.4
@@ -21,30 +21,35 @@
WSIF can now be found on the Apache web site since WSIF was donated to
Apache a few months ago.
Version available from
-<a href="http://www.alphaworks.ibm.com/";>Alphaworks</a>
+<a href="http://www.alphaworks.ibm.com/tech/wsif";>Alphaworks</a>
is no longer maintained and will be soon retired.
<p>
The Apache WSIF homepage can be found at:
-<a
href="http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-axis-wsif/java/readme.htm?rev=HEAD&content-type=text/html";>http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-axis-wsif/java/readme.htm?rev=HEAD&content-type=text/html
+<a href="http://xml.apache.org/axis/wsif";>http://xml.apache.org/axis/wsif
</a>
<p>
Nightly builds are available at
-<a
href="http://xml.apache.org/dist/axis/nightly/";>http://xml.apache.org/dist/axis/nightly/</a>
+<a href="http://cvs.apache.org/dist/axis/nightly/";
target="_blank">http://cvs.apache.org/dist/axis/nightly/</a>
+The wsif-src*.zip contains source distribution, the
+wsif-bin* zip file contains a built wsif.jar along with the API Javadoc and
+the wsif-all*.zip contains the source, the JAR and the javadocs. (* will be
+replaced by the current version number in the file names).
+<h2>What are differences between WSIF and WSTK?</h2>
-The xml-axis-wsif-src.zip contains source distribution and
-wsif-bin zip file contains a built wsif.jar along with the API Javadoc.
+<p>WSIF is a framework for invoking WSDL-described services. WSTK is IBM's Web
Services Toolkit, a preview technology for web services support in Websphere available
from alphaworks. WSTK includes WSIF amongst other things.</p>
-<h2>What are differences between WSIF and WSTK?</h2>
+<h2>What are differences between WSIF and Axis?</h2>
-<p>TODO
+<p>Axis is an implementation of SOAP. It includes on the server-side infrastructure
for deploying web service implementations and then routing SOAP messages between
clients and those implementations. It also implements the JAX-RPC specification for
invoking SOAP services.</p>
+<p>WSIF is similar to the client piece of Axis, in that it is used for invoking
services. However, WSIF's API is WSDL-driven and protocol independent; it allows
protocol-specific code ("providers") to be plugged in. For invoking SOAP services,
WSIF is in fact packaged with an Axis provider, that uses Axis APIs (i.e. JAX-RPC) to
do the invocation. So WSIF operates at a more abstract level than Axis.</p>
<h2>What are differences between WSIF and JAX-RPC?</h2>
-<p>TODO
+<p>JAX-RPC is an API for invoking XML-based RPC services - essentially its current
scope is limited to invocation of SOAP services. WSIF is an API for invoking
WSDL-described services, whether they happen to be SOAP services or not (for example,
WSIF defines WSDL bindings so that EJBs, enterprise software acessible using JMS or
the Java Connector architecture as wel as local java classes can all be described as
first class WSDL services and then invoked using the same, protocol-independent WSIF
API).</p>
<h2>How to use and set HTTP proxy with WSIF and SOAP over HTTP</h2>
@@ -52,14 +57,24 @@
<h2>Where are extensions to WSDL that are supported by WSIF documented?</h2>
-<p>This is described in <a href="how_to_wsdl_extensions.htm">separate
document</a>.</p>
-
-
-<h2>How to write WSIF provider for new WSDL binding?</h2>
-
-<p>This is described in <a href="how_to_provider.htm">separate document</a>.
+<p>WSIF defines and supports the following WSDL bindings (besides the standard SOAP
binding which is supported):
+ <ul>
+ <li><a href="wsdl_extensions/java_extension.html">Local java binding
extensions for WSDL</a></li>
+ <li><a href="wsdl_extensions/ejb_extension.html">EJB binding extensions for
WSDL</a></li>
+ <li><a href="wsdl_extensions/jms_bindings.htm">JMS binding extensions for
WSDL</a></li>
+ <li><a href="wsdl_extensions/j2c_extensions/wsif_j2c_extensions.htm">JCA
binding extensions for WSDL</a></li>
+ </ul>
+</p>
+<p>This means that using the WSIF API you can invoke a service, independent of
whether it is made available over SOAP, as an EJB, over JMS, using java connectors or
as a local java class.</p>
+
+<h2>How do I define my own WSDL binding extensions and write WSIF providers for
them</h2>
+
+ Here's <a href="how_to_wsdl_extensions.htm">how to write your own WSDL
+ extensions to support new protocols</a>, and then
+ <a href="how_to_provider.htm">write your own WSIF
+ providers to support customized WSIF extensions</a>.
-<h2>How to report problems and request new features?</h2>
+<h2>How do I report problems and request new features?</h2>
<p>Please subscribe and post your questions to
<a href="http://xml.apache.org/axis/mail.html";>AXIS mailing list</a>
@@ -67,18 +82,18 @@
-<h2>How to select SOAP provider used in WSIF?</h2>
+<h2>How do I select SOAP provider used in WSIF?</h2>
WSIF comes with an Apache Axis provider so using axis with WSIF is easy.
WSIF has two SOAP providers, one using Apache SOAP 2.3 and the other using Axis,
-by default WSIF will use the SOAP 2.3 provider. The default is controlled by the
+by default WSIF will use the Axis provider. The default is controlled by the
org.apache.wsif.util.WSIFPluggableProviders class. The javadoc for this class
gives details of how the default is defined, but it can be overridden
programmatically, for example, the following call sets the axis provider to be
the
default:<br>
<tt>WSIFPluggableProviders.overrideDefaultProvider("http://schemas.xmlsoap.org/wsdl/soap/";,</tt><br>
-<tt>new WSIFDynamicProvider_ApacheAxis() );</tt><br>
+<tt>new WSIFDynamicProvider_ApacheSOAP() );</tt><br>
<h2>How to use dynamic invoker sample?</h2>
@@ -101,13 +116,14 @@
<p>WSIF does support complex types - of course XML schema
support is limited (but very reasonable).
-<p>You may be referring to DynamicInvoker sample that does not
-support complex types however take look on AddressBook sample instead.
+<p>The DynamicInvoker doesn't support invocation of services using
+complex types since this requires that java representations of the
+complex types be generated first.
<p>It is also possible to extend DynamicInvoker to support
-complex type but it will require some kind of intermediate
+complex types but it will require some kind of intermediate
representation of values that can handle any complex type
-(such as using JROM...)
+(such as <a href="http://www.alphaworks.ibm.com/tech/jrom";>JROM</a>...)
<hr width="100%">
