You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pubscribe-commits@ws.apache.org by jr...@apache.org on 2005/07/30 02:52:24 UTC
svn commit: r226448 - in
/webservices/pubscribe/trunk/src/site/content/xdocs/dev_guide: client.xml
debug.xml deploy.xml
Author: jruzzi
Date: Fri Jul 29 17:52:18 2005
New Revision: 226448
URL: http://svn.apache.org/viewcvs?rev=226448&view=rev
Log:
ian edits
Modified:
webservices/pubscribe/trunk/src/site/content/xdocs/dev_guide/client.xml
webservices/pubscribe/trunk/src/site/content/xdocs/dev_guide/debug.xml
webservices/pubscribe/trunk/src/site/content/xdocs/dev_guide/deploy.xml
Modified: webservices/pubscribe/trunk/src/site/content/xdocs/dev_guide/client.xml
URL: http://svn.apache.org/viewcvs/webservices/pubscribe/trunk/src/site/content/xdocs/dev_guide/client.xml?rev=226448&r1=226447&r2=226448&view=diff
==============================================================================
--- webservices/pubscribe/trunk/src/site/content/xdocs/dev_guide/client.xml (original)
+++ webservices/pubscribe/trunk/src/site/content/xdocs/dev_guide/client.xml Fri Jul 29 17:52:18 2005
@@ -8,7 +8,7 @@
<body>
<section id="intro">
<title>Introduction</title>
- <p>Pubscribe includes a lightweight SOAP client that is used to test your services. The client is invoked using an Ant script, which is located in
+ <p>Pubscribe includes a lightweight SOAP client that can be used to test your services. The client is invoked using an Ant script, which is located in
<code>INSTALL_DIR/template/soapclient.xml</code>. Request and response messages are viewed in the Ant output. This section explains how to use the client and
how to build request SOAP messages for the client.</p>
</section>
@@ -17,8 +17,7 @@
<p>The client reads a <code>.soap</code> file which contains the SOAP envelope to be sent. Examples of SOAP files are located in
<code>INSTALL_DIR/examples/filesystem/requests/</code>. Each file is named appropriately based on the operation it contains. Use these files as models when
creating your own .soap files. Make sure you modify the resource identifier in the WS-Addressing header to match the entry that is in the JNDI
- configuration file and the resource indentifier number for the instance you would like to invoke. This has to do with the home's implementation of
- <code>init()</code> and allows you to decide which instances are valid for sending requests.</p>
+ configuration file and the resource id for the instance you would like to invoke. The id is used by the invocation framework to lookup a particular resource instance.</p>
</section>
<section>
<title>Running the Client</title>
@@ -32,7 +31,7 @@
</p>
</li>
</ol>
- <note>You can add an entry to <code>build.properties</code> for <code>url</code> which will alleviate the need
+ <note>You can add an entry to <code>build.properties</code> for the <code>url</code> property, which alleviates the need
to specify it on the command line.</note>
</section>
</body>
Modified: webservices/pubscribe/trunk/src/site/content/xdocs/dev_guide/debug.xml
URL: http://svn.apache.org/viewcvs/webservices/pubscribe/trunk/src/site/content/xdocs/dev_guide/debug.xml?rev=226448&r1=226447&r2=226448&view=diff
==============================================================================
--- webservices/pubscribe/trunk/src/site/content/xdocs/dev_guide/debug.xml (original)
+++ webservices/pubscribe/trunk/src/site/content/xdocs/dev_guide/debug.xml Fri Jul 29 17:52:18 2005
@@ -15,12 +15,14 @@
</section>
<section>
<title>Changing Log Levels</title>
- <p>Log4j uses the following log levels: DEBUG, INFO, WARN, ERROR, and FATAL. By default, Pubscribe is configured to emit INFO messages. To see more
- detailed log messages, you must change the log level. The following example assumes Tomcat.</p>
+ <p>Log4j uses the following log levels: DEBUG, INFO, WARN, ERROR, and FATAL. By default, Apache WSRF is configured at the INFO level, which means messages logged
+ at INFO or higher level (i.e. INFO, WARN, ERROR, and FATAL) are included in the output. To see more detailed log messages, you must change the log level.
+ The following example assumes Tomcat.
+ </p>
<p>To change the logging level:</p>
<ol>
<li>Using a text editor, open the log4j.properties file located in the WEB-INF/classes directory of the deployed Pubscribe Web application.</li>
- <li>Change the log level associated with the <code>log4j.category.org.apache.ws</code> package. For example:<source>
+ <li>Change the log level associated with all classes below the <code>log4j.category.org.apache.ws</code> package. For example:<source>
log4j.category.org.apache.ws=DEBUG</source>
</li>
<li>Save the log4j.properties file.</li>
Modified: webservices/pubscribe/trunk/src/site/content/xdocs/dev_guide/deploy.xml
URL: http://svn.apache.org/viewcvs/webservices/pubscribe/trunk/src/site/content/xdocs/dev_guide/deploy.xml?rev=226448&r1=226447&r2=226448&view=diff
==============================================================================
--- webservices/pubscribe/trunk/src/site/content/xdocs/dev_guide/deploy.xml (original)
+++ webservices/pubscribe/trunk/src/site/content/xdocs/dev_guide/deploy.xml Fri Jul 29 17:52:18 2005
@@ -92,17 +92,16 @@
alternative, you can use the following markers which are replaced at runtime:
</p>
<ul>
- <li><code>$IP_ADDRESS$</code> - An attempt is made to determine the IP address at runtime. (Do not use on multi-homed systems).</li>
- <li><code>$HOST_NAME$</code> - An attempt is made to determine the host name at runtime.</li>
+ <li>
+ <code>$IP_ADDRESS$</code> - An attempt is made to determine the IP address at runtime. (Do not use on multi-homed systems).</li>
+ <li>
+ <code>$HOST_NAME$</code> - An attempt is made to determine the host name at runtime.</li>
</ul>
- <p>The <code>resourceIdentifierReferenceParameterName</code> represents the name of the WS-Addressing-header that is used to
- extract a unique resource identifier to lookup a specific WS resource instance. This value should be a QName that includes the local
- reference parameter name in the format <em>
- <code>{target namespace}qualified name of a reference parameter</code>
- </em>. If you omit
- this entry, it is assumed that the service is a <strong>
- <code>SINGLETON</code>
- </strong> service and no resource id is expected in the
+ <p>The <code>resourceIdentifierReferenceParameterName</code> parameter represents the name of the WS-Addressing-header that is used to
+ extract a unique resource identifier to lookup a specific WS-Resource instance. This value should be a QName that includes the local
+ reference parameter name in the format <em><code>{namespaceURI}localPart</code></em>, where namesapaceURI and localPart are the namespace and URI and local
+ part of the qualified name of the reference paramater that should contain the resource identifier. If you omit this entry, it is assumed that the service is a
+ <strong><code>SINGLETON</code></strong> service and no resource id is expected in the
WS-Addressing headers.
</p>
</li>