You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wsif-dev@ws.apache.org by ow...@apache.org on 2003/07/18 13:04:53 UTC
cvs commit: xml-axis-wsif/java/doc faq.html
owenb 2003/07/18 04:04:52
Modified: java/doc/wsdl_extensions ejb_extension.html
java/doc faq.html
Log:
update to FAQ and correction to ejb extension info
Revision Changes Path
1.3 +1 -1 xml-axis-wsif/java/doc/wsdl_extensions/ejb_extension.html
Index: ejb_extension.html
===================================================================
RCS file: /home/cvs/xml-axis-wsif/java/doc/wsdl_extensions/ejb_extension.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- ejb_extension.html 16 Dec 2002 11:33:37 -0000 1.2
+++ ejb_extension.html 18 Jul 2003 11:04:52 -0000 1.3
@@ -66,7 +66,7 @@
<li><b><tt>ejb:address</tt></b>
<p>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.</p>
-<p>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 service provider to insure that all java methods used for mapping abstract operations must be publicly available through the specified interface in the EJB.</p>
+<p>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 upto 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.</p>
</ul>
<h4>Example:</h4>
1.2 +46 -2 xml-axis-wsif/java/doc/faq.html
Index: faq.html
===================================================================
RCS file: /home/cvs/xml-axis-wsif/java/doc/faq.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- faq.html 14 Jan 2003 14:19:08 -0000 1.1
+++ faq.html 18 Jul 2003 11:04:52 -0000 1.2
@@ -51,9 +51,53 @@
<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>
+<h2>How do I set an HTTP proxy to be used by WSIF?</h2>
+<p>HTTP proxy settings can be set using the following system properties</p>
+<ul>
-<p>TODO: describe here current support for system properties etc.
+<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>
+
+<h2>How can I configure WSIF to work through an authenticating proxy server?</h2>
+<p><b>Note:</b>
+The following applies to the latest nightly builds and is not available in WSIF 2.0
+</p>
+<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>
<h2>Where are extensions to WSDL that are supported by WSIF documented?</h2>