[prev in list] [next in list] [prev in thread] [next in thread]
List: wsrf-commits
Subject: svn commit: r208686 - in /webservices/wsrf/trunk/src/site/content/xdocs: ./
From: jruzzi () apache ! org
Date: 2005-06-30 21:19:16
Message-ID: 20050630211918.35472.qmail () minotaur ! apache ! org
[Download RAW message or body]
Author: jruzzi
Date: Thu Jun 30 14:19:13 2005
New Revision: 208686
URL: http://svn.apache.org/viewcvs?rev=208686&view=rev
Log:
content update
Modified:
webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/deploy.xml
webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/service.xml
webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/wsdl_tool.xml
webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/wsrf_wsdl.xml
webservices/wsrf/trunk/src/site/content/xdocs/getting_started.xml
webservices/wsrf/trunk/src/site/content/xdocs/site.xml
webservices/wsrf/trunk/src/site/content/xdocs/tutorial/setup.xml
webservices/wsrf/trunk/src/site/content/xdocs/tutorial/webapp.xml
webservices/wsrf/trunk/src/site/content/xdocs/tutorial/wsdl.xml
webservices/wsrf/trunk/src/site/content/xdocs/tutorial/wsdl2java.xml
Modified: webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/deploy.xml
URL: http://svn.apache.org/viewcvs/webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/deploy.xml?rev=208686&r1=208685&r2=208686&view=diff
==============================================================================
--- webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/deploy.xml (original)
+++ webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/deploy.xml Thu Jun 30 \
14:19:13 2005 @@ -8,14 +8,31 @@
<body>
<section id="intro">
<title>Introduction</title>
- <p>Once you've written and compiled the required classes, you will need to deploy
- your service to the webapp. The distribution contains a \
<code>webapps</code> directory which
- contains a <code>wsrf</code> webapp. An Ant script is provided for \
deploying the FileSystem
- example. We will discuss how the script works so you will be able to \
build your
- own scripts.</p>
+ <p>The quickest way to deploy your WS Resource is to use the generated build \
scripts. The scripts compile and delploy your WS + Resource to the Apache WSRF Web \
application, which is an Apache-Axis Web application. This section describes how to \
use the + generated build scripts and also how the script works so you can build \
your own scripts.</p> + </section>
+ <section>
+ <title>Using the generated build scripts</title>
+ <p>The Wsdl2Java tool generates an Ant build script that is used to compile and \
deploy your WS Resource. The script is located in the + output directory under the \
subdirectory for you WS Resource (e.g., \
<code>generated/</code><em><code>service_name</code> + </em>).</p>
+ <p>To compile and deploy using the Ant script</p>
+ <ol>
+ <li>In your output directory, edit build.properties and modify the \
<code>wsrf.webapp.dir</code>. If you are using + Tomcat and have \
<code>CATALINA_HOME</code> set, you do not need to modify this property.</li> \
+ <li>From a command prompt, change directories to \
<code>generated/</code><em><code>service_name</code></em></li> + <li>Run:</li>
+ </ol>
+ <source><![CDATA[
+ ant compile deploy ]]></source>
+
+ <p>Start Tomcat and verify that the service is deployed by going to
+ <a href="http://localhost:8080/wsrf/servlet/AxisServlet">http://localhost:8080/wsrf/servlet/AxisServlet</a>
+ </p>
</section>
<section id="steps">
- <title>How to manually deploy your service</title>
+ <title>Manually Deploying your Service</title>
<p>In this section we will describe how to manually deploy your service. We will \
describe each step in the process.</p> <ol>
<li>
@@ -90,34 +107,5 @@
</li>
</ol>
</section>
- <section id="filesys">
- <title>Deploying the FileSystem Example</title>
- <p>To deploy the FileSystem example we will need to generate XmlBean code from \
the WSDL,
- compile all classes and deploy it to the webapp. An Ant script is \
provided for handling
- all of these steps.
- </p>
- <p>You should make sure to copy the Apache WSRF webapp from the included webapps \
directory to your <code>TOMCAT_HOME/webapps </code> directory, and that the \
environment variable <code>CATALINA_HOME</code> is set and pointing to your Tomcat \
installation.
- </p>
- <p>You will need to change your directory to the <code>docs/tutorial</code> \
directory. You will then
- need to run the command:
- </p>
- <p>
- <strong>
- <code>>ant generate</code>
- </strong>
- </p>
- <p>You will now need to change your directory to the \
<code>docs/tutorial/generated/filesystem</code> directory. You will \
need
- to replace the <code>FilesystemResource.init()</code> and<code> \
FilesystemHome.getInstance(..)</code> (generated under src) methods with the \
contents of the files in the directory \
<code>docs/tutorial/generated/filesystem/method_impls</code>
- </p>
- <p>You will then need to run the command:</p>
- <p>
- <strong>
- <code>>ant compile deploy</code>
- </strong>
- </p>
- <p>This will compile and deploy the code. You can now start Tomcat.</p>
- <note>This step assumes you have installed Apache Ant. If not, you can get it <a \
href="http://ant.apache.org/">here</a>
- </note>
- </section>
- </body>
+ </body>
</document>
Modified: webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/service.xml
URL: http://svn.apache.org/viewcvs/webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/service.xml?rev=208686&r1=208685&r2=208686&view=diff
==============================================================================
--- webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/service.xml (original)
+++ webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/service.xml Thu Jun 30 \
14:19:13 2005 @@ -106,11 +106,15 @@
* Initialization method.
*/
public void init( );</source>
- <p>The <code>getMethodNameMap()</code> returns a SoapMethodNameMap \
implementation which contains mappings of WSDL operation QNames to Java method \
names. If you have custom operations you will need to create an instance of \
<code>ServiceSoapMethodName</code> and add mappings for your operations. + <p>The \
<code>getMethodNameMap()</code> returns a SoapMethodNameMap implementation which \
contains mappings of WSDL + operation QNames to Java method names. If you have \
custom operations you will need to create an instance of \
+ <code>ServiceSoapMethodName</code> and add mappings for your operations. </p>
- <p>The <code>getResourceContext()</code> operation returns the ResourceContext \
associated with this service. This method may be left abstract in this class \
and later implemented in the Service extension of your abstract class. + <p>The \
<code>getResourceContext()</code> operation returns the ResourceContext associated \
with this service. This method may be + left abstract in this class and later \
implemented in the Service extension of your abstract class. </p>
- <p>The<code> init()</code> method is provided to give you an opportunity to \
initialize members for your Service (e.g. <code>ServiceSoapMethodName \
</code>)</p> + <p>The<code> init()</code> method is provided to give you an \
opportunity to initialize members for your Service + (e.g. \
<code>ServiceSoapMethodName </code>)</p> </section>
<section id="classvars">
<title>Class Variables</title>
@@ -132,28 +136,37 @@
</section>
<section id="ops">
<title>Operations</title>
- <p>The operations which are defined in the abstract class should be operations \
which typically should not need to be touched. The specification operations are \
a prime example. Upon looking at the <code>AbstractFileSystem</code> class, we see \
the operations defined for methods like: \
<code>getMultipleResourceProperties(..)</code>. The body of these methods are \
similar in that they hand the invocation off to a Provider class: + <p>The \
operations which are defined in the abstract class should be operations which \
typically should not need to be touched. The + specification operations are a \
prime example. Upon looking at the <code>AbstractFileSystem</code> class, we see the \
operations + defined for methods like: \
<code>getMultipleResourceProperties(..)</code>. The body of these methods are \
similar in that they hand the + invocation off to a Provider class:
</p>
<source>public GetMultipleResourcePropertiesResponseDocument \
getMultipleResourceProperties( GetMultipleResourcePropertiesDocument requestDoc ) {
return new GetMultipleResourcePropertiesProvider( getResourceContext( ) \
).getMultipleResourceProperties( requestDoc ); }</source>
- <p>Notice the <code>GetMultipleResourcePropertiesProvider</code> class being \
used. Providers are used to handle the specification method calls. It provides \
a way to encapsulate the functionalty needed to handle a method call for a specific \
specification. Each specification operation will have an equivalent *Provider \
class to handle a particular class.</p> + <p>Notice the \
<code>GetMultipleResourcePropertiesProvider</code> class being used. Providers are \
used to handle the specification + method calls. It provides a way to \
encapsulate the functionalty needed to handle a method call for a specific \
specification. Each + specification operation will have an equivalent *Provider \
class to handle a particular class.</p> <p>The packages:
<strong>
<code>org.apache.ws.resource.properties.porttype.impl</code>
</strong> and
<strong>
<code>org.apache.ws.resource.lifetime.porttype.impl</code>
- </strong> contain the Providers for the methods of the specifications. \
You should refer to these packages when implementing the specification operations. \
+ </strong> contain the Providers for the methods of the specifications. + \
You should refer to these packages when implementing the specification operations. \
</p> </section>
</section>
<section id="service">
- <title>The Service class.</title>
- <p>The service class is the extension of the abstract class we previously \
outlined. Because of the extension you will need to implement the required \
method <code>getResourceContext()</code>. The ResourceContext should be passed in \
the constructor to the class and be maintained as a class variable. The \
ResourceContext will be passed, upon construction, to the Service via the Home class. \
+ <title>The Service class</title> + <p>The service class is the extension of \
the abstract class we previously outlined. Because of the extension you will need to \
implement the + required method <code>getResourceContext()</code>. The \
ResourceContext should be passed in the constructor to the class and be \
+ maintained as a class variable. The ResourceContext will be passed, upon \
construction, to the Service via the Home class. </p>
- <p>The Service class should contain any custom operations as were defined in the \
WSDL for the service. The safest way to handle the parameters and return type of \
the methods is to simply use <code>XmlObject</code>: + <p>The Service class should \
contain any custom operations as were defined in the WSDL for the service. The \
safest way to handle the + parameters and return type of the methods is to simply \
use <code>XmlObject</code>: </p>
<source> public XmlObject mount( XmlObject requestDoc )
{
Modified: webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/wsdl_tool.xml
URL: http://svn.apache.org/viewcvs/webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/wsdl_tool.xml?rev=208686&r1=208685&r2=208686&view=diff
==============================================================================
--- webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/wsdl_tool.xml (original)
+++ webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/wsdl_tool.xml Thu Jun 30 \
14:19:13 2005 @@ -3,27 +3,139 @@
"http://forrest.apache.org/dtd/document-v20.dtd">
<document>
<header>
- <title>Using the WSDL2Java Class</title>
+ <title>Using Wsdl2Java</title>
</header>
<body>
<section>
- <title>Using the Ant Task</title>
- <p>The Wsdl2Java tool is invoked using an Ant task, as shown by the following \
example:</p> + <title>Introduction</title>
+ <p>The Wsdl2Java tool is used to generate a set of artificats for a WS Resource. \
The artifiacts include:</p> + <ul>
+ <li>A set of Java classes based on the WSDL definition. This includes a \
servicen, resource, and + home class. Some of the Java code will need to be \
manually edited after the files are generated.</li> + <li>Interfaces for custom \
operations.</li> + <li>Java bindings for all Types that are defined in the WSDL. \
The interfaces and classes are + created using the <a \
href="ext:xmlbeans.apache.org">XMLBeans</a> schema compiler</li> + <li>an Axis Web \
Service Deployment Descriptor (WSDD) for your service (<em>service</em>_deploy.wsdd). \
This file is used to deploy your service to + Axis.</li>
+ <li>A JNDI Resource configuration file for your service \
(<em>service</em>_jndi-config.xml. The file contains JNDI information about your \
service/resource and + generated home.</li>
+ </ul>
+ <p>The tool saves you a great deal of time, since these files do not have to be \
created from scratch. You simply pass the tool a WSRF WSDL and the files + are \
automatically generated. You can use the tool directly or you can use an Ant task. \
+ </p> + </section>
+ <section>
+ <title>Ant Task</title>
+ <p>The Wsdl2Java tool can be invoked using the <code>wsdl2Java</code> Ant task \
(<code>org.apache.ws.resource.tool.Wsdl2JavaTask</code>). The \
+ <code>INSTALL_DIR/template/build.xml</code> script contains a target that already \
implements this task.</p> + <p>To use the target:</p>
+ <ol>
+ <li>copy INSTALL_DIR/template/build.xml and build.properties to any directory. \
This directory will be referred to as <code>WORK_DIR</code>.</li> + <li>Open \
build.properties and modify the <code>wsrf.webapp.dir</code> property and any proxy \
settings if applicable.</li> + <li>Copy your WSRF WSDL to <code>WORK_DIR</code>. \
If your WSDL depends on a schema that is not accessible over the network, you must \
copy the + schema to this directory as well.</li>
+ <li>From a command prompt, change directories to <code>WORK_DIR</code>.</li>
+ <li>Run the following command and then check the <code>WORK_DIR/generated</code> \
directory to see the generated files.</li> + </ol>
<source><![CDATA[
- <property name="wsrf.webapp.dir" location="${wsrf.home}/webapps/wsrf" />
-
- <path id="wsrf.classpath.id">
+ ant generate ]]></source>
+ <section>
+ <title>Task Definition</title>
+ <p>The task is defined as follows :</p>
+ <source><![CDATA[
+<taskdef name="wsdl2Java"
+ classname="org.apache.ws.resource.tool.Wsdl2JavaTask"
+ classpath="path/to/wsrf.jar" /> ]]></source>
+ <p>
+ <strong>Parameters</strong>
+ </p>
+ <p>The task takes the following parameters:</p>
+ <table>
+ <tr>
+ <th>Attribute</th>
+ <th>Description</th>
+ <th>Required</th>
+ </tr>
+ <tr>
+ <td>wsdl</td>
+ <td>Enter the full path to a WSRF WSDL file.</td>
+ <td>Yes, unless a <code>wsdls</code> parameter is used. </td>
+ </tr>
+ <tr>
+ <td>wsdls</td>
+ <td>Entered as a nested element following the rules of fileset. This parameter \
is used instead of the <code>wsdl</code> parameter to indicate multiple + WSRF \
WSDLs to be converted.</td> + <td>No</td>
+ </tr>
+ <tr>
+ <td>classpath</td>
+ <td>The classpath to be passed to the XMLBeans schema compiler. The classpath \
should reference the <code>INSTALL_DIR/wsrf/webapp/lib</code> + and \
<code>/classes</code> directories.</td> + <td>Yes</td>
+ </tr>
+ <tr>
+ <td>classpathref</td>
+ <td>Adds a classpath, given as reference to a path defined elsewhere.</td>
+ <td>No</td>
+ </tr>
+ <tr>
+ <td>outputdir</td>
+ <td>Enter a directory where the generated files will be placed.</td>
+ <td>Yes</td>
+ </tr>
+ <tr>
+ <td>verbose</td>
+ <td>Enter <code>true</code> to increase build message output.</td>
+ <td>No, default is <code>false</code>
+ </td>
+ </tr>
+ <tr>
+ <td>proxyHost</td>
+ <td>Enter the Host IP address of a proxy that is used to connect to the \
Internet.</td> + <td>No</td>
+ </tr>
+ <tr>
+ <td>proxyPort</td>
+ <td>Enter the Port number of a proxy that is used to connect to the \
Internet.</td> + <td>No</td>
+ </tr>
+ <tr>
+ <td>nonProxyHosts</td>
+ <td>Enter the Host IP address separated by "|" to indicate Hosts that do not \
require a proxy.</td> + <td>No</td>
+ </tr>
+ </table>
+ <p>
+ <strong>Example</strong>
+ </p>
+ <p>The following example generates files for a single WSDL and places the \
generated files in a directory + named <code>/generated</code>. To simplify the \
example, the classpath is referenced. You must set the <code>${wsrf.home}</code> Ant \
property to <code> + INSTALL_DIR</code> (e.g. /opt/wsrf-1.0beta).</p> \
<source><![CDATA[ +
+ <property name="wsrf.webapp.dir" location="${wsrf.home}/webapps/wsrf" />
+ <path id="wsrf.classpath.id">
<pathelement location="${wsrf.webapp.dir}/WEB-INF/classes" />
<fileset dir="${wsrf.webapp.dir}/WEB-INF/lib" includes="*.jar" />
</path>
- <taskdef name="wsdl2Java" \
classname="org.apache.ws.resource.tool.Wsdl2JavaTask" \
classpathref="wsrf.classpath.id" /> + <taskdef name="wsdl2Java" \
classname="org.apache.ws.resource.tool.Wsdl2JavaTask" classpath="wsrf.classpath.id" \
/>
<wsdl2Java wsdl="path/to/your.wsdl"
outputdir="generated"
- classpathref="wsrf.classpath.id" />
- ]]></source>
- <note>The wsrf.home Ant property used above has to be set to \
<code>INSTALL_DIR</code> (e.g. /opt/wsrf-1.0beta).</note> + \
classpath="wsrf.classpath.id" />]]></source> +
+ <p>If you want to generate the files for multiple WSDLs, you can \
use:</p><source><![CDATA[ +
+ <wsdl2Java outputdir="generated" classpath="wsrf.classpath.id" />
+ <wsdls dir="path/to/wsdls/">
+ <include name="**/*.wsdl" />
+ </wsdls>
+ </wsdl2Java>]]></source>
+ </section>
+ </section>
+ <section>
+ <title>Main Class</title>
+ <p>TODO</p>
</section>
</body>
</document>
Modified: webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/wsrf_wsdl.xml
URL: http://svn.apache.org/viewcvs/webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/wsrf_wsdl.xml?rev=208686&r1=208685&r2=208686&view=diff
==============================================================================
--- webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/wsrf_wsdl.xml (original)
+++ webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/wsrf_wsdl.xml Thu Jun 30 \
14:19:13 2005 @@ -9,13 +9,13 @@
<section>
<title>Using the WSRF WSDL Template</title>
<p>Resources are exposed as WSRF WS-Resources using the Web Services Description \
Language (WSDL). The WSDL must
- conform to the conventions as described in the WSRF specifications. To expedite \
the WSDL creation process, a
- WSRF WSDL template is provided. The template contains both common and \
required
- sections as well as detailed instructions.
+ conform to the conventions as described in the <a href="site:wsrf">WSRF \
Specifications</a>. To make it easier to write a + WSRF WSDL, Apache WSRF provides \
a template WSDL that can be used as a starting point. The template saves a good deal \
of time + and is less error-prone than writing a WSRF-compliant WSDL from scratch. \
</p>
<p>To use the template:</p>
<ol>
- <li>Using a text or XML editor, open \
INSTALL_DIR/docs/tutorial/_TEMPLATE_.wsdl.</li> + <li>Using a text or XML editor, \
open <code>INSTALL_DIR/template/_TEMPLATE_.wsdl</code>.</li>
<li>Save the file with a new name (e.g., <em>nameOfYourService</em>.wsdl).</li>
<li>Modify your WSDL based on the instructions in the template and the \
information below.</li> </ol>
@@ -23,10 +23,17 @@
</section>
<section>
<title>Defining the WSRF PortType</title>
- <p>A WSRF WSDL should contain only one portType, which is an aggregation of \
custom
- resource-specific operations and operations from the following
- specification-defined portTypes:
+ <p>A WSRF WSDL should contain only one portType. The portType aggregates \
operations from WSRF specification-defined portTypes + and custom \
resource-specific operations. The specification-defined portTypes that are discussed \
below include: </p>
+ <ul>
+ <li>WS-ResourceProperties (WSRF-RP) PortTypes</li>
+ <li>WS-ResourceLifetime (WSRF-RL) PortTypes</li>
+ </ul>
+ <p>If you've copied the WSDL template file as described above, your WSDL file
+ already contains a WSRF-compliant portType. You simply have to rename the \
portType (<code>MyPortType</code>) and uncomment the + blocks \
corresponding to whichever optional portTypes you want your WS-Resource to support. + \
</p> <section>
<title>WS-ResourceProperties (WSRF-RP) PortTypes</title>
<table>
@@ -80,24 +87,18 @@
</td>
</tr>
</table>
- <note>In addition to operations, the ScheduledResourceTermination portType also \
includes two properties.
- This means that if a WS-Resource implements this portType, it must expose \
these properties.</note>
- </section>
- <p>The PortType element must have a
- {http://docs.oasis-open.org/wsrf/2004/11/wsrf-WS-ResourceProperties-1.2-draft-05.xsd}ResourceProperties
- attribute whose value is the QName of the resource properties document \
element defined + <note>In addition to operations, the \
<code>ScheduledResourceTermination</code> portType also includes two properties. If a \
+ WS-Resource implements this portType, it must also expose these \
properties.</note> + <p>The PortType element must have a
+ <code>{http://docs.oasis-open.org/wsrf/2004/11/wsrf-WS-ResourceProperties-1.2-draft-05.xsd}ResourceProperties</code>
+ attribute whose value is the <code>QName</code> of the resource \
properties document element defined in the types/schema section of the WSDL file.
</p>
- <p>If you've copied the WSDL template file as described above, your WSDL file
- already contains a WSRF portType. You simply have to uncomment the blocks
- corresponding to whichever optional portTypes you want your WS-Resource to \
support. You should also
- add any custom operations you want your WS-Resource to expose. The \
following
- section describes how to add custom operations.
- </p>
+ </section>
</section>
<section>
<title>Adding Custom Operations</title>
- <p>You may optionally add custom operations to the WSRF portType. To do so,
+ <p>Custom operations can be added to the WSRF portType. To do so,
you will have to define message types, messages, and operations, as you \
would
for any WSDL. It is recommended that, when defining your custom operations,
you adhere to the rules defined by
Modified: webservices/wsrf/trunk/src/site/content/xdocs/getting_started.xml
URL: http://svn.apache.org/viewcvs/webservices/wsrf/trunk/src/site/content/xdocs/getting_started.xml?rev=208686&r1=208685&r2=208686&view=diff
==============================================================================
--- webservices/wsrf/trunk/src/site/content/xdocs/getting_started.xml (original)
+++ webservices/wsrf/trunk/src/site/content/xdocs/getting_started.xml Thu Jun 30 \
14:19:13 2005 @@ -64,10 +64,7 @@
following command:
<source><![CDATA[
-ant -f soapclient.xml -Durl=http://localhost:8080/wsrf/services/filesystem \
-Dxml=requests/GetMultipleResourceProperties.soap]]>
- </source>
-
- <br/>
+ant -f soapclient.xml -Durl=http://localhost:8080/wsrf/services/filesystem \
-Dxml=requests/GetMultipleResourceProperties.soap]]></source>
<br/>You should also try other request messages kept under the \
<code>requests</code> sub-directory.</li> </ol>
</section>
Modified: webservices/wsrf/trunk/src/site/content/xdocs/site.xml
URL: http://svn.apache.org/viewcvs/webservices/wsrf/trunk/src/site/content/xdocs/site.xml?rev=208686&r1=208685&r2=208686&view=diff
==============================================================================
--- webservices/wsrf/trunk/src/site/content/xdocs/site.xml (original)
+++ webservices/wsrf/trunk/src/site/content/xdocs/site.xml Thu Jun 30 14:19:13 2005
@@ -44,11 +44,11 @@
<developer label="Developer Guide" href="dev_guide/" tab="doc">
<dev label="Overview" href="index.html"/>
<compose label="Composing a WSRF WSDL" href="wsrf_wsdl.html"/>
- <tool label="Using the WSDL2Java Tool" href="wsdl_tool.html"/>
- <service label="Service Class" href="home.html"/>
- <resource label="Write Resource Class" href="resource.html"/>
- <callback label="Write Callback Objects" href="callback.html"/>
- <home label="Write Home Class" href="home.html"/>
+ <tool label="Using Wsdl2Java" href="wsdl_tool.html"/>
+ <service label="Service Class" href="service.html"/>
+ <resource label="Resource Class" href="resource.html"/>
+ <home label="Home Class" href="home.html"/>
+ <callback label="Callback Objects" href="callback.html"/>
<deploy label="Deploying" href="deploy.html"/>
<client label="Useing the SOAP Client" href="client.html"/>
</developer>
Modified: webservices/wsrf/trunk/src/site/content/xdocs/tutorial/setup.xml
URL: http://svn.apache.org/viewcvs/webservices/wsrf/trunk/src/site/content/xdocs/tutorial/setup.xml?rev=208686&r1=208685&r2=208686&view=diff
==============================================================================
--- webservices/wsrf/trunk/src/site/content/xdocs/tutorial/setup.xml (original)
+++ webservices/wsrf/trunk/src/site/content/xdocs/tutorial/setup.xml Thu Jun 30 \
14:19:13 2005 @@ -24,8 +24,9 @@
<li>Using a text editor, open <code>WORK_DIR/build.properties</code>.</li>
<li>Uncomment the <code>wsrf.webapp.dir</code> property and set it to the \
location where the WSRF Web application is installed. If you are \
using
Tomcat and have <code>CATALINA_HOME</code> set, you do not need to modify this \
property.</li> + <li>Uncomment and modify the proxy settings if you require a \
proxy to connect to external Web sites.</li> + <li>Save and close \
build.properties.</li> </ol>
- <note>Uncomment and modify the proxy settings if you require a proxy to connect \
to external Web sites.</note> <p>
<img src="images/back.gif" alt="go to the previous step"/>
<a href="site:tut">Back</a>
Modified: webservices/wsrf/trunk/src/site/content/xdocs/tutorial/webapp.xml
URL: http://svn.apache.org/viewcvs/webservices/wsrf/trunk/src/site/content/xdocs/tutorial/webapp.xml?rev=208686&r1=208685&r2=208686&view=diff
==============================================================================
--- webservices/wsrf/trunk/src/site/content/xdocs/tutorial/webapp.xml (original)
+++ webservices/wsrf/trunk/src/site/content/xdocs/tutorial/webapp.xml Thu Jun 30 \
14:19:13 2005 @@ -10,19 +10,20 @@
<title>Introduction</title>
<p>In this step of the tutorial, the filesystem example code and the generated \
classes are compiled and deployed
to the WSRF Web application. An Ant script is provided for compiling and \
deploying. Detailed instructions for
- using and modifying the Ant script is provided in the <a \
href="site:deploy">Developer Guide</a>. + using the Ant script are provided in the \
<a href="site:deploy">Developer Guide</a>. </p>
</section>
<section>
<title>Run the Compile/Deploy Ant Script</title>
<p>To compile and deploy the service:</p>
<ol>
- <li>Copy <code>INSTALL_DIR/examples/filesystem/src/java/example</code>to \
<code>WORK_DIR/generated/filesystem/src/java</code>.</li> + <li>Copy \
<code>INSTALL_DIR/examples/filesystem/src/java/example</code> to \
+ <code>WORK_DIR/generated/filesystem/src/java</code>.</li>
<li>From a command prompt, change directories to \
<code>WORK_DIR/generated/filesystem</code>.</li>
<li>Run <code>ant compile deploy</code>. The service is compiled and deployed to \
the WSRF Web application.</li> <li>Start Tomcat if it is not already started.</li>
- <li>Using a browser, go to <a \
href="http://doc-lab.americas.hpqcorp.net:8080/wsrf/servlet/AxisServlet">http://doc-
- lab.americas.hpqcorp.net:8080/wsrf/servlet/AxisServlet</a> and verify that the \
filesystem service is deployed. + <li>Using a browser, go to <a \
href="http://doc-lab.americas.hpqcorp.net:8080/wsrf/servlet/AxisServlet"> \
+ http://doc-lab.americas.hpqcorp.net:8080/wsrf/servlet/AxisServlet</a> and verify \
that the filesystem service is deployed. </li>
</ol>
<note>Please refer to the Tomcat and Axis documentation if you do not know how to \
start Tomcat.</note>
Modified: webservices/wsrf/trunk/src/site/content/xdocs/tutorial/wsdl.xml
URL: http://svn.apache.org/viewcvs/webservices/wsrf/trunk/src/site/content/xdocs/tutorial/wsdl.xml?rev=208686&r1=208685&r2=208686&view=diff
==============================================================================
--- webservices/wsrf/trunk/src/site/content/xdocs/tutorial/wsdl.xml (original)
+++ webservices/wsrf/trunk/src/site/content/xdocs/tutorial/wsdl.xml Thu Jun 30 \
14:19:13 2005 @@ -17,7 +17,7 @@
good practice to use the template if you are not familiar with the WSRF family of \
specifications. Detailed instructions for composing a WSRF-compliant WSDL using the \
template are provided in the <a href="site:compose">Developer Guide</a>. </p>
- <p>The FileSystem WSDL is an example of a WSRF WSDL that contains a \
single portType + <p>The FileSystem WSDL is an example of a WSRF WSDL that \
contains a single portType (<code>FileSystemPortType</code>), which exposes all of \
the optional portTypes defined by the WSRF-RP and WSRF-RL specifications. It also \
defines two custom operations, <code>Mount</code> and <code>Unmount</code>, and a \
group of custom resource properties.
@@ -25,7 +25,7 @@
</section>
<section>
<title>Copy the FileSystem WSDL</title>
- <p>Copy <code>INSTALL_DIR/examples/filesystem/src/wsdl/FileSystem.wsdl</code>to \
<code>WORK_DIR</code>.</p> + <p>Copy \
<code>INSTALL_DIR/examples/filesystem/src/wsdl/FileSystem.wsdl</code> to \
<code>WORK_DIR</code>.</p> <p>
<img src="images/back.gif" alt="go to the previous step"/>
<a href="site:setup">Back</a>
Modified: webservices/wsrf/trunk/src/site/content/xdocs/tutorial/wsdl2java.xml
URL: http://svn.apache.org/viewcvs/webservices/wsrf/trunk/src/site/content/xdocs/tutorial/wsdl2java.xml?rev=208686&r1=208685&r2=208686&view=diff
==============================================================================
--- webservices/wsrf/trunk/src/site/content/xdocs/tutorial/wsdl2java.xml (original)
+++ webservices/wsrf/trunk/src/site/content/xdocs/tutorial/wsdl2java.xml Thu Jun 30 \
14:19:13 2005 @@ -12,7 +12,8 @@
as its input and outputs the following artificats:
</p>
<ul>
- <li><a href="ext:xmlbeans.apache.org">XMLBeans</a> for all XML Schema types and \
elements defined in the types section of the WSDL</li> + <li>
+ <a href="ext:xmlbeans.apache.org">XMLBeans</a> for all XML Schema types and \
elements defined in the types section of the WSDL</li> <li>an abstract base Resource \
class</li> <li>a Resource class</li>
<li>an abstract base Service class</li>
@@ -27,7 +28,7 @@
</section>
<section>
<title>Generating the Artifacts</title>
- <p>The Ant script (<code>WORKING_DIR/build.xml</code>) contains a target for the \
Wsdl2Java tool. To generate the artifacts for the + <p>The Ant script \
(<code>WORK_DIR/build.xml</code>) contains a target for the Wsdl2Java tool. To \
generate the artifacts for the filesystem example:</p>
<ol>
<li>From a command prompt, change directories to <code>WORK_DIR</code>.</li>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic