owenb 2003/07/18 03:38:02
Modified: targets/wsif/providers ejb_provider.html java_provider.html
apacheaxis_provider.pdf index.pdf ejb_provider.pdf
index.html java_provider.pdf
apachesoap_provider.html apacheaxis_provider.html
apachesoap_provider.pdf
targets/wsif faq.pdf changes.html changes.pdf faq.html
bugs.html
targets/wsif/providers/wsdl_extensions ejb_extension.pdf
ejb_extension.html
Log:
updates to FAQ, provider information and copyright dates
Revision Changes Path
1.4 +14 -1 ws-site/targets/wsif/providers/ejb_provider.html
Index: ejb_provider.html
===================================================================
RCS file: /home/cvs/ws-site/targets/wsif/providers/ejb_provider.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- ejb_provider.html 8 Apr 2003 10:49:25 -0000 1.3
+++ ejb_provider.html 18 Jul 2003 10:37:58 -0000 1.4
@@ -202,7 +202,20 @@
</tr>
</table>
-<p>WORK IN PROGRESS</p>
+<p>The EJB provider allows the invocation of remote EJBs. It relies on two WSDL
exstensions
+ </p>
+
+<ul>
+
+<li>
+<a href="wsdl_extensions/ejb_extension.html">EJB extension</a>
+</li>
+
+<li>
+<a href="wsdl_extensions/formattypemapping_extension.html">Format binding
extension</a>
+</li>
+
+</ul>
</div>
</td><td width="10"><img width="10" height="1" alt=""
src="../skin/images/spacer.gif"></td>
1.4 +14 -1 ws-site/targets/wsif/providers/java_provider.html
Index: java_provider.html
===================================================================
RCS file: /home/cvs/ws-site/targets/wsif/providers/java_provider.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- java_provider.html 8 Apr 2003 10:49:25 -0000 1.3
+++ java_provider.html 18 Jul 2003 10:37:59 -0000 1.4
@@ -202,7 +202,20 @@
</tr>
</table>
-<p>WORK IN PROGRESS</p>
+<p>The Java provider allows the invocation of local Java classes. It relies on two
WSDL exstensions
+ </p>
+
+<ul>
+
+<li>
+<a href="wsdl_extensions/java_extension.html">Java extension</a>
+</li>
+
+<li>
+<a href="wsdl_extensions/formattypemapping_extension.html">Format binding
extension</a>
+</li>
+
+</ul>
</div>
</td><td width="10"><img width="10" height="1" alt=""
src="../skin/images/spacer.gif"></td>
1.2 +21 -13 ws-site/targets/wsif/providers/apacheaxis_provider.pdf
<<Binary file>>
1.3 +10 -10 ws-site/targets/wsif/providers/index.pdf
<<Binary file>>
1.2 +138 -15 ws-site/targets/wsif/providers/ejb_provider.pdf
<<Binary file>>
1.5 +1 -1 ws-site/targets/wsif/providers/index.html
Index: index.html
===================================================================
RCS file: /home/cvs/ws-site/targets/wsif/providers/index.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- index.html 8 Apr 2003 10:49:25 -0000 1.4
+++ index.html 18 Jul 2003 10:37:59 -0000 1.5
@@ -202,7 +202,7 @@
</tr>
</table>
-<p>Information on the differenent providers shipped with WSIF and also the WSDL
extensions used by these providers</p>
+<p>Information on the different providers shipped with WSIF and also the WSDL
extensions used by these providers</p>
</div>
</td><td width="10"><img width="10" height="1" alt=""
src="../skin/images/spacer.gif"></td>
1.2 +86 -15 ws-site/targets/wsif/providers/java_provider.pdf
<<Binary file>>
1.4 +1 -1 ws-site/targets/wsif/providers/apachesoap_provider.html
Index: apachesoap_provider.html
===================================================================
RCS file: /home/cvs/ws-site/targets/wsif/providers/apachesoap_provider.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- apachesoap_provider.html 8 Apr 2003 10:49:25 -0000 1.3
+++ apachesoap_provider.html 18 Jul 2003 10:37:59 -0000 1.4
@@ -202,7 +202,7 @@
</tr>
</table>
-<p>WORK IN PROGRESS</p>
+<p>The Apache SOAP provider allows WSIF to invoke SOAP services via the use of
Apache SOAP</p>
</div>
</td><td width="10"><img width="10" height="1" alt=""
src="../skin/images/spacer.gif"></td>
1.4 +6 -1 ws-site/targets/wsif/providers/apacheaxis_provider.html
Index: apacheaxis_provider.html
===================================================================
RCS file: /home/cvs/ws-site/targets/wsif/providers/apacheaxis_provider.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- apacheaxis_provider.html 8 Apr 2003 10:49:25 -0000 1.3
+++ apacheaxis_provider.html 18 Jul 2003 10:37:59 -0000 1.4
@@ -202,7 +202,12 @@
</tr>
</table>
-<p>WORK IN PROGRESS</p>
+<p>The Apache Axis provider allows WSIF to invoke SOAP services via the use of
Apache Axis</p>
+
+<p>
+The Axis provider offers a greater level of function than the Apache SOAP provider
and it is for this reason that it
+is the default soap provider i.e. the default provider for the <span
class="codefrag">http://schemas.xmlsoap.org/wsdl/soap/</span> namespace.
+ </p>
</div>
</td><td width="10"><img width="10" height="1" alt=""
src="../skin/images/spacer.gif"></td>
1.2 +10 -10 ws-site/targets/wsif/providers/apachesoap_provider.pdf
<<Binary file>>
1.5 +883 -616 ws-site/targets/wsif/faq.pdf
<<Binary file>>
1.6 +2 -2 ws-site/targets/wsif/changes.html
Index: changes.html
===================================================================
RCS file: /home/cvs/ws-site/targets/wsif/changes.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- changes.html 8 Apr 2003 10:49:24 -0000 1.5
+++ changes.html 18 Jul 2003 10:38:00 -0000 1.6
@@ -233,7 +233,7 @@
<li>
<a href="#N10008">Version 2.0 (27th Jan 2003)</a>
</li>
-</ul>
+</ul>
<a name="N10008"></a>
<h3>Version 2.0 (27th Jan 2003)</h3>
@@ -378,7 +378,7 @@
</tr>
<tr>
<td colspan="2" bgcolor="#CFDCED" class="copyright" align="center"><font size="2"
face="Arial, Helvetica, Sans-Serif">Copyright ©
- 2002 The Apache Software Foundation. All rights reserved.<script
type="text/javascript" language="JavaScript"><!--
+ 2003 The Apache Software Foundation. All rights reserved.<script
type="text/javascript" language="JavaScript"><!--
document.write(" - "+"Last Published: " + document.lastModified);
// --></script></font></td>
</tr>
1.4 +71 -84 ws-site/targets/wsif/changes.pdf
<<Binary file>>
1.7 +76 -27 ws-site/targets/wsif/faq.html
Index: faq.html
===================================================================
RCS file: /home/cvs/ws-site/targets/wsif/faq.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- faq.html 8 Apr 2003 10:49:24 -0000 1.6
+++ faq.html 18 Jul 2003 10:38:00 -0000 1.7
@@ -245,30 +245,33 @@
<a name="faq-N1003A-menu"></a><a href="#faq-N1003A">What are the differences
between WSIF and JAX-RPC?</a>
</li>
<li>
-<a name="faq-N10046-menu"></a><a href="#faq-N10046">How to use and set HTTP proxy
with WSIF and SOAP over HTTP</a>
+<a name="faq-N10046-menu"></a><a href="#faq-N10046">How do I set an HTTP proxy to
be used by WSIF?</a>
</li>
<li>
-<a name="faq-N10052-menu"></a><a href="#faq-N10052">Where can I find details of the
extensions to WSDL that are supported by WSIF?</a>
+<a name="faq-N10064-menu"></a><a href="#faq-N10064">How can I configure WSIF to
work through an authenticating proxy server?</a>
</li>
<li>
-<a name="faq-N10062-menu"></a><a href="#faq-N10062">How do I define my own WSDL
binding extensions and write WSIF providers for them</a>
+<a name="faq-N10093-menu"></a><a href="#faq-N10093">Where can I find details of the
extensions to WSDL that are supported by WSIF?</a>
</li>
<li>
-<a name="faq-N10076-menu"></a><a href="#faq-N10076">How do I report problems and
request new features?</a>
+<a name="faq-N100A3-menu"></a><a href="#faq-N100A3">How do I define my own WSDL
binding extensions and write WSIF providers for them</a>
</li>
<li>
-<a name="faq-N10086-menu"></a><a href="#faq-N10086">How do I select SOAP provider
used in WSIF?</a>
+<a name="faq-N100B7-menu"></a><a href="#faq-N100B7">How do I report problems and
request new features?</a>
</li>
<li>
-<a name="faq-N10097-menu"></a><a href="#faq-N10097">How do I use use dynamic
invoker sample?</a>
+<a name="faq-N100C7-menu"></a><a href="#faq-N100C7">How do I select SOAP provider
used in WSIF?</a>
</li>
<li>
-<a name="faq-N100A4-menu"></a><a href="#faq-N100A4">Sample DynamicInvoker and
Complex Type handling in WSIF?</a>
+<a name="faq-N100D8-menu"></a><a href="#faq-N100D8">How do I use use dynamic
invoker sample?</a>
+</li>
+<li>
+<a name="faq-N100E5-menu"></a><a href="#faq-N100E5">Sample DynamicInvoker and
Complex Type handling in WSIF?</a>
</li>
</ul>
-<a name="N10042"></a>
+<a name="N10047"></a>
<h3>Answers</h3>
-<a name="N10045"></a><a name="faq-N10005"></a>
+<a name="N1004A"></a><a name="faq-N10005"></a>
<h4>1. What is the official version of WSIF? How to I get the latest version?</h4>
<p>
The official version of WSIF is found here on the Apache web site.
@@ -285,39 +288,85 @@
<a href="http://www.alphaworks.ibm.com/";>Alphaworks</a>
is no longer maintained.
</p>
-<a name="N1005B"></a><a name="faq-N1001F"></a>
+<a name="N10060"></a><a name="faq-N1001F"></a>
<h4>2. What are the differences between WSIF and WSTK?</h4>
<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>
-<a name="N10063"></a><a name="faq-N1002B"></a>
+<a name="N10068"></a><a name="faq-N1002B"></a>
<h4>3. What are the differences between WSIF and Axis?</h4>
<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>
-<a name="N1006E"></a><a name="faq-N1003A"></a>
+<a name="N10073"></a><a name="faq-N1003A"></a>
<h4>4. What are the differences between WSIF and JAX-RPC?</h4>
<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>
-<a name="N10076"></a><a name="faq-N10046"></a>
-<h4>5. How to use and set HTTP proxy with WSIF and SOAP over HTTP</h4>
-<p>TODO: describe here current support for system properties etc.</p>
-<a name="N1007E"></a><a name="faq-N10052"></a>
-<h4>6. Where can I find details of the extensions to WSDL that are supported by
WSIF?</h4>
+<a name="N1007B"></a><a name="faq-N10046"></a>
+<h4>5. How do I set an HTTP proxy to be used by WSIF?</h4>
+<p>HTTP proxy settings can be set using the following system properties</p>
+<ul>
+
+<li>
+<span class="codefrag">http.proxyHost</span> - The hostname of the proxy
server</li>
+
+<li>
+<span class="codefrag">http.proxyPort</span> - The port for the proxy server</li>
+
+<li>
+<span class="codefrag">http.nonProxyHosts</span> - A comma separated list of hosts
to access directly rather than through the proxy</li>
+
+</ul>
+<a name="N10095"></a><a name="faq-N10064"></a>
+<h4>6. How can I configure WSIF to work through an authenticating proxy server?</h4>
+<div class="frame note">
+<div class="label">Note</div>
+<div class="content">The following applies to the latest nightly builds and is not
available in WSIF 2.0</div>
+</div>
+<p>In order to retrieve and parse a wsdl document from behind an
+authenticating proxy, you can use the WSIFUtils.readWSDLThroughAuthProxy
+method. Assuming a username of <em>fred</em> and password of <em>cat</em> then
use:</p>
+<pre class="code">
+String wsdlLoc = "http://someserver.com/somedoc.wsdl";
+char[] passwd = "cat".toCharArray();
+java.net.PasswordAuthentication pa = new java.net.PasswordAuthentication("fred", c);
+Definition def = WSIFUtils.readWSDLThroughAuthProxy(wsdlLoc, pa);
+</pre>
+<p>
+If using the Axis provider, you can invoke a service through an
+authenticating proxy by setting proxy usernames and passwords in one of two
+ways:</p>
+<ol>
+
+<li>Set system properties <span class="codefrag">http.proxyUser</span> and <span
class="codefrag">http.proxyPassword</span> or</li>
+
+<li>Set the username and password on the context message used by the service
+via:</li>
+
+</ol>
+<pre class="code">
+ WSIFService service = ..... /// Get from factory
+ WSIFMessage ctx = service.getContext();
+ ctx.setObjectPart(WSIFConstants.CONTEXT_HTTP_PROXY_USER, "fred");
+ ctx.setObjectPart(WSIFConstants.CONTEXT_HTTP_PROXY_PWSD, "cat");
+ service.setContext(ctx);
+ </pre>
+<a name="N100C0"></a><a name="faq-N10093"></a>
+<h4>7. Where can I find details of the extensions to WSDL that are supported by
WSIF?</h4>
<p>Links to the supported extensions can be found in the <a
href="providers/index.html">providers </a>section.
</p>
-<a name="N1008A"></a><a name="faq-N10062"></a>
-<h4>7. How do I define my own WSDL binding extensions and write WSIF providers for
them</h4>
+<a name="N100CC"></a><a name="faq-N100A3"></a>
+<h4>8. How do I define my own WSDL binding extensions and write WSIF providers for
them</h4>
<p>Here's <a href="developers/how_to_wsdl_extensions.html">how to write your own
WSDL extensions</a> to support new protocols, and then
<a href="developers/how_to_provider.html">write your own WSIF providers</a> to
support customized WSIF extensions.</p>
-<a name="N1009A"></a><a name="faq-N10076"></a>
-<h4>8. How do I report problems and request new features?</h4>
+<a name="N100DC"></a><a name="faq-N100B7"></a>
+<h4>9. How do I report problems and request new features?</h4>
<p>The <a href="mail.html">mailing lists</a> are what you are looking for</p>
-<a name="N100A6"></a><a name="faq-N10086"></a>
-<h4>9. How do I select SOAP provider used in WSIF?</h4>
+<a name="N100E8"></a><a name="faq-N100C7"></a>
+<h4>10. How do I select SOAP provider used in WSIF?</h4>
<p>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 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
@@ -327,8 +376,8 @@
new WSIFDynamicProvider_ApacheSOAP() );</span>
</p>
-<a name="N100B3"></a><a name="faq-N10097"></a>
-<h4>10. How do I use use dynamic invoker sample?</h4>
+<a name="N100F5"></a><a name="faq-N100D8"></a>
+<h4>11. How do I use use dynamic invoker sample?</h4>
<pre class="code">java clients.DynamicInvoker
http://www.xmethods.net/sd/2001/TemperatureService.wsdl getTemp 10570
Reading WSDL document from 'http://www.xmethods.net/sd/2001/TemperatureService.wsdl'
@@ -342,8 +391,8 @@
Done!
</pre>
-<a name="N100BC"></a><a name="faq-N100A4"></a>
-<h4>11. Sample DynamicInvoker and Complex Type handling in WSIF?</h4>
+<a name="N100FE"></a><a name="faq-N100E5"></a>
+<h4>12. Sample DynamicInvoker and Complex Type handling in WSIF?</h4>
<p>WSIF does support complex types - of course XML schema support is limited (but
very reasonable).</p>
<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>
<p>It is also possible to extend DynamicInvoker to support complex types but it
will require some kind of intermediate representation of values that can handle any
complex type
1.7 +1 -1 ws-site/targets/wsif/bugs.html
Index: bugs.html
===================================================================
RCS file: /home/cvs/ws-site/targets/wsif/bugs.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- bugs.html 8 Apr 2003 10:49:24 -0000 1.6
+++ bugs.html 18 Jul 2003 10:38:00 -0000 1.7
@@ -299,7 +299,7 @@
</tr>
<tr>
<td colspan="2" bgcolor="#CFDCED" class="copyright" align="center"><font size="2"
face="Arial, Helvetica, Sans-Serif">Copyright ©
- 2002 The Apache Software Foundation. All rights reserved.<script
type="text/javascript" language="JavaScript"><!--
+ 2003 The Apache Software Foundation. All rights reserved.<script
type="text/javascript" language="JavaScript"><!--
document.write(" - "+"Last Published: " + document.lastModified);
// --></script></font></td>
</tr>
1.3 +38 -38 ws-site/targets/wsif/providers/wsdl_extensions/ejb_extension.pdf
<<Binary file>>
1.4 +6 -8
ws-site/targets/wsif/providers/wsdl_extensions/ejb_extension.html
Index: ejb_extension.html
===================================================================
RCS file:
/home/cvs/ws-site/targets/wsif/providers/wsdl_extensions/ejb_extension.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- ejb_extension.html 8 Apr 2003 10:49:26 -0000 1.3
+++ ejb_extension.html 18 Jul 2003 10:38:01 -0000 1.4
@@ -206,7 +206,7 @@
<a href="#N1000C">Details</a>
</li>
<li>
-<a href="#N10067">Example</a>
+<a href="#N10061">Example</a>
</li>
</ul>
@@ -243,8 +243,7 @@
className="nmtoken"
jndiName="nmtoken"?
initialContextFactory="nmtoken"?
- jndiProviderURL="url"?
- archive="nmtoken"? />
+ jndiProviderURL="url"? />
</port>
</service>
</definitions>
@@ -279,16 +278,15 @@
This element is an extension under the WSDL <em>port</em> element that allows
specification of an EJB object as an endpoint for a service available via
the EJB binding. The port whose address is specified this way must be associated
with an EJB binding only.<br>
<br>
-The <em>className</em> attribute specifies the fully qualified name of the home
interface class of the EJB. The optional <em>jndiName</em> attribute
-specifies the name under which this EJB can be looked up in a JNDI context. The
<em>initialContextFactory</em> and <em>jndiProviderURL</em> attributes
-complete the set if information required to perform a JNDI lookup for the EJB. The
optional <em>classLoader</em> attribute specifies the class loader to
-be used for loading the service class, and the optional <em>archive</em> attribute
is the location of a jar file that the client would need. It is upto
+The <em>className</em> attribute specifies the fully qualified name of the home
interface class of the EJB. The <em>jndiName</em> attribute
+specifies the name under which this EJB can be looked up in a JNDI context. The
optional <em>initialContextFactory</em> and <em>jndiProviderURL</em> attributes
+complete the set if information required to perform a JNDI lookup for the EJB. It
is up to
the service provider to insure that all java methods used for mapping abstract
operations must be publicly available through the specified interface in the EJB.
</li>
</ul>
-<a name="N10067"></a>
+<a name="N10061"></a>
<h3>Example</h3>
<pre class="code">
<?xml version="1.0" ?>
