You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-commits@ws.apache.org by da...@apache.org on 2006/09/18 17:56:37 UTC
svn commit: r447446 - in /webservices/muse/site/docs/2.0.0/tutorial:
01-install-muse.html 04-review-artifacts-osgi.html
07-deploy-application-osgi.html 08-test-client.html
Author: danj
Date: Mon Sep 18 08:56:36 2006
New Revision: 447446
URL: http://svn.apache.org/viewvc?view=rev&rev=447446
Log:
simple formatting, HTML (use of <br> and <ul>), and capitalization fixes.
Modified:
webservices/muse/site/docs/2.0.0/tutorial/01-install-muse.html
webservices/muse/site/docs/2.0.0/tutorial/04-review-artifacts-osgi.html
webservices/muse/site/docs/2.0.0/tutorial/07-deploy-application-osgi.html
webservices/muse/site/docs/2.0.0/tutorial/08-test-client.html
Modified: webservices/muse/site/docs/2.0.0/tutorial/01-install-muse.html
URL: http://svn.apache.org/viewvc/webservices/muse/site/docs/2.0.0/tutorial/01-install-muse.html?view=diff&rev=447446&r1=447445&r2=447446
==============================================================================
--- webservices/muse/site/docs/2.0.0/tutorial/01-install-muse.html (original)
+++ webservices/muse/site/docs/2.0.0/tutorial/01-install-muse.html Mon Sep 18 08:56:36 2006
@@ -123,8 +123,8 @@
<a name="N1000C"></a><a name="latest-release"></a>
<h2 class="boxed">Get the Latest Release</h2>
<div class="section">
- <p>Go to the <a href="../../../download.html#v2.0.0">download page</a> and download the binary distribution.</p>
- <p>Unzip the package into a directory on your machine.</p>
+ <p>Go to the <a href="../../../download.html#v2.0.0">download page</a> and download the binary distribution.
+ Unzip the package into a directory on your machine.</p>
</div>
<a name="N10016"></a><a name="review-contents"></a>
@@ -167,26 +167,30 @@
</div>
<p>Here is an explanation of the contents of each directory:
<ul>
- <li><b>/bin</b> - contains wrapper scripts for executing <a href="../manual/tools/wsdl2java.html">wsdl2java</a> and <a href="../manual/tools/wsdlmerge.html">wsdlmerge</a>. There are batch scripts (<em>.bat</em> extension) for Windows machines and shell scripts (<em>.sh</em> extension, uses standard <em>/bin/sh</em>). For convenience, this would be the directory that you would add to your system's executable search path.</li><br/>
- <li><b>/docs</b> - contains the documentation you are currently reading. Click <a href="../index.html">here</a> to go back to the table of contents.</li><br/>
- <li><b>/lib</b> - contains libraries and template project directories for code generation. More specifically the commandline tools (<a href="../manual/tools/wsdl2java.html">wsdl2java</a> and <a href="../manual/tools/wsdlmerge.html">wsdlmerge</a>) use the jars under <b>/common</b> when they are invoke. <a href="../manual/tools/wsdl2java.html">wsdl2java</a> uses the files in <b>/axis2</b> and <b>/eclipse-osgi</b> to create projects for Axis2 J2EE projects and OSGi projects respectively.</li><br/>
+ <li><b>/bin</b> - contains scripts for executing <a href="../manual/tools/wsdl2java.html">wsdl2java</a> and <a href="../manual/tools/wsdlmerge.html">wsdlmerge</a>. There are batch scripts (<em>.bat</em> extension) for Windows machines and shell scripts (<em>.sh</em> extension, uses standard <em>/bin/sh</em>). For convenience, this would be the directory that you would add to your system's executable search path.<br/></li><br/>
+ <li><b>/docs</b> - contains the documentation you are currently reading.<br/></li><br/>
+ <li><b>/lib</b> - contains libraries and template project directories for code generation. More specifically the command line
+ tools (<a href="../manual/tools/wsdl2java.html">wsdl2java</a> and <a href="../manual/tools/wsdlmerge.html">wsdlmerge</a>) use
+ the jars under <b>/common</b> when they are invoke. The <a href="../manual/tools/wsdl2java.html">wsdl2java</a> tool uses the
+ files in <b>/axis2</b> and <b>/eclipse-osgi</b> to create projects for Axis2 J2EE projects and OSGi projects respectively.<br/></li><br/>
<ul>
- <li><b>/axis2</b> - A expanded template WAR from the Axis2 project which is populated with project specific files (class files, descriptors) during code generation.</li><br/>
- <li><b>/common</b> - Common jars including Xerces XML Parser, XStream and WSDL4j.</li><br/>
- <li><b>/eclipse-osgi</b> - Jars from the Eclipse project that are used to create the minimum environment necessary to launch
- an endpoint that is to be deployed on the OSGi platform.</li><br/>
+ <li><b>/axis2</b> - an expanded template WAR from the Axis2 project.<br/></li><br/>
+ <li><b>/common</b> - common third-party libraries, including the Apache Xerces XML Parser, XStream and WSDL4J.<br/></li><br/>
+ <li><b>/eclipse-osgi</b> - components from the Eclipse project that provide the minimum OSGi environment needed to host
+ a Muse-based application.<br/></li><br/>
</ul>
- <li><b>/modules</b> - contains the jars that contain the muse runtime and tooling implementation.</li><br/>
+ <li><b>/modules</b> - contains the jars that contain the muse runtime and tooling implementation.<br/></li><br/>
<ul>
- <li><b>/axis2</b> - contains Axis2-specific jars.</li><br/>
- <li><b>/core</b> - contains jars used throughout the runtime.</li><br/>
- <li><b>/osgi</b> - contains osgi-related jars.</li><br/>
- <li><b>/tools</b> - contains the tooling jar.</li><br/>
- <li><b>/ws-fx-api</b> - contains the interfaces for WS-* implementations.</li><br/>
- <li><b>/ws-fx-impl</b> - contains concrete implementations of the WS-* specifications supported by Muse.</li><br/>
+ <li><b>/axis2</b> - contains support for Axis2 deployment.<br/></li><br/>
+ <li><b>/core</b> - contains jars that are essential to all Muse applications.<br/></li><br/>
+ <li><b>/osgi</b> - contains support for OSGi deployment.<br/></li><br/>
+ <li><b>/tools</b> - contains the code generation and resource analysis tools.<br/></li><br/>
+ <li><b>/ws-fx-api</b> - contains the Java interfaces for WS-* specifications.<br/></li><br/>
+ <li><b>/ws-fx-impl</b> - contains Muse's default implementations of the WS-* specifications.<br/></li><br/>
</ul>
- <li><b>/samples</b> - contains samples, see the <a href="../manual/index.html#samples">documentation</a>.</li><br/>
- <li><b>license.txt</b> - A copy of the Apache License.</li><br/>
+ <li><b>/samples</b> - contains <a href="../manual/index.html#samples">sample projects</a> that exercise the
+ various WS-* specs.<br/></li><br/>
+ <li><b>license.txt</b> - A copy of the Apache Muse licensing terms (ASF License 2.0).<br/></li><br/>
</ul>
</p>
</p>
Modified: webservices/muse/site/docs/2.0.0/tutorial/04-review-artifacts-osgi.html
URL: http://svn.apache.org/viewvc/webservices/muse/site/docs/2.0.0/tutorial/04-review-artifacts-osgi.html?view=diff&rev=447446&r1=447445&r2=447446
==============================================================================
--- webservices/muse/site/docs/2.0.0/tutorial/04-review-artifacts-osgi.html (original)
+++ webservices/muse/site/docs/2.0.0/tutorial/04-review-artifacts-osgi.html Mon Sep 18 08:56:36 2006
@@ -190,7 +190,7 @@
</code>
</div>
</div>
-There are two things to note in the activator. <br/><br/>
+There are two things to note in the activator: <br/><br/>
First, the <code>data.location</code> System property is used to allow the user to specify a particular location in the file system for storing
logs and resource persistence information. The value will be interpreted as a <code>File</code> path, and used accordingly. If the value is <code>"USE_BUNDLE_DATA"</code>, then the Bundle data location (as described in the OSGi
specification) is used. If no value is provide for this property, the default is the root of the Bundle's install location. This location is determined
@@ -201,7 +201,7 @@
due to an implemntation detail within the <code>FileLocator</code> class, but the end result is that the <code>org.eclipse.equinox.common</code> must be active in order for your Bundle to execute. If an
alternative mechanism is used to set your Bundle's root location, then the dependency on <code>org.eclipse.equinox.common</code> may be removed from the
activator and the Manifest.
-</br><br/>
+<br/><br/>
Users wishing to specify unique locations per Bundle, or to mix the location handling implementation between Bundles should change the Activator accordingly.
</div>
@@ -240,25 +240,29 @@
<br><br>
<ul>
-<li>Require-Bundle - This header specifies the additional Bundles required in the OSGi runtime to allow your Bundle to run. These bundles are described below:
-<br/><ul>muse.osgi.core - the OSGi-specific bits of the Muse runtime.</ul>
-<br/><ul>muse.osgi.soa.axis2 - the Muse axis2 isolation layer</ul>
-<br/><ul>muse.osgi.soa.core - a generic SOA service definition layer that will allow bindings to other SOAP engines.</ul>
-<br/><ul>muse.core - the Muse runtime, packaged for OSGi.</ul>
-<br/><ul>muse.util.all - various Muse utilities, packaged for OSGi.</ul>
-<br/><ul>muse.wsa.soap - the Muse implementation of WS-Adressing, along with its spec-related artifacts.</ul>
-<br/><ul>muse.wsrf.api - the Muse interfaces for implementing WSRF, along with its spec-related artifacts.</ul>
-<br/><ul>muse.wsrf.impl - the default implementations of the WSRF capabilities.</ul>
-<br/><ul>muse.wsn.api - the Muse interfaces for implementing WSN, along with its spec-related artifacts.</ul>
-<br/><ul>muse.wsn.impl - the default implementations of the WSN capabilities.</ul>
-<br/><ul>org.eclipse.corona.soa.provider.Axis2 - a Bundle hosting an Axis2 instance, and implementing the service definition specified by <code>muse.osgi.soa.core</code>.</ul>
-<br/><ul>org.eclipse.equinox.http - A Bundle implementing the OSGi HTTP service, which is consumed by the.</ul>
-<br/><ul>org.eclipse.equinox.servlet.api - A Bundle exporting the <code>javax.servlet</code> and <code>javax.servlet.http</code> packages.</ul>
-<br/><ul>org.eclipse.osgi.services - the OSGi service interfaces, including the HTTP service interface definition.</ul>
-<br/><ul>org.eclipse.osgi.util - some OSGi utility services.</ul>
-<br/><ul>org.eclipse.osgi - the Eclipse Equinox implementation of OSGi.</ul>
-<br/><ul>org.eclipse.equinox.common - some Eclipse-specific extensions (including the <code>FileLocator</code> used in the Bundle <code>Activator</code>) to the OSGi runtime. </ul>
-<br/></li><br/>
+<li>Require-Bundle - This header specifies the additional Bundles required in the OSGi runtime to allow your Bundle to run.
+These bundles are described below:
+<ul>
+<li>muse.osgi.core - the OSGi-specific bits of the Muse runtime.<br/></li><br/>
+<li>muse.osgi.soa.axis2 - the Muse axis2 isolation layer<br/></li><br/>
+<li>muse.osgi.soa.core - a generic SOA service definition layer that will allow bindings to other SOAP engines.<br/></li><br/>
+<li>muse.core - the Muse runtime, packaged for OSGi.<br/></li><br/>
+<li>muse.util.all - various Muse utilities, packaged for OSGi.<br/></li><br/>
+<li>muse.wsa.soap - the Muse implementation of WS-Adressing, along with its spec-related artifacts.<br/></li><br/>
+<li>muse.wsrf.api - the Muse interfaces for implementing WSRF, along with its spec-related artifacts.<br/></li><br/>
+<li>muse.wsrf.impl - the default implementations of the WSRF capabilities.<br/></li><br/>
+<li>muse.wsn.api - the Muse interfaces for implementing WSN, along with its spec-related artifacts.<br/></li><br/>
+<li>muse.wsn.impl - the default implementations of the WSN capabilities.<br/></li><br/>
+<li>org.eclipse.corona.soa.provider.Axis2 - a Bundle hosting an Axis2 instance, and implementing the service definition specified by <code>muse.osgi.soa.core</code>.<br/></li><br/>
+<li>org.eclipse.equinox.http - A Bundle implementing the OSGi HTTP service, which is consumed by the.<br/></li><br/>
+<li>org.eclipse.equinox.servlet.api - A Bundle exporting the <code>javax.servlet</code> and <code>javax.servlet.http</code> packages.<br/></li><br/>
+<li>org.eclipse.osgi.services - the OSGi service interfaces, including the HTTP service interface definition.<br/></li><br/>
+<li>org.eclipse.osgi.util - some OSGi utility services.<br/></li><br/>
+<li>org.eclipse.osgi - the Eclipse Equinox implementation of OSGi.<br/></li><br/>
+<li>org.eclipse.equinox.common - some Eclipse-specific extensions (including the <code>FileLocator</code>
+used in the Bundle <code>Activator</code>) to the OSGi runtime. <br/></li><br/>
+</ul>
+</li>
<li>MUSE-CONFIG - This header specifies the location of the muse.xml file relative to the Bundle class path. The tooling ensures that the Bundle's root location is on the classpath;
by convention the muse.xml is placed in the OSGI-INF directory, which appears under the Bundle root.
<br/></li><br/>
@@ -267,7 +271,6 @@
<br/></li><br/>
</ul>
</li>
-<br/></li><br/>
<li><b>/OSGI-INF/muse/muse.xml</b> - This is the Muse deployment descriptor. It is read by Muse at initialization in order to load, configure, and support the resource types that you have implemented.
<br/></li><br/>
<li><b>/OSGI-INF/wsdl</b> - This directory holds the WSDL and related schema files for the resource type implemented in the sample.
Modified: webservices/muse/site/docs/2.0.0/tutorial/07-deploy-application-osgi.html
URL: http://svn.apache.org/viewvc/webservices/muse/site/docs/2.0.0/tutorial/07-deploy-application-osgi.html?view=diff&rev=447446&r1=447445&r2=447446
==============================================================================
--- webservices/muse/site/docs/2.0.0/tutorial/07-deploy-application-osgi.html (original)
+++ webservices/muse/site/docs/2.0.0/tutorial/07-deploy-application-osgi.html Mon Sep 18 08:56:36 2006
@@ -118,9 +118,9 @@
name of the Bundle, you need to change the name of the directory.
</p>
<p>
-A copy of <a href="http://www.eclipse.org/equinox/" class="external">Equinox</a> is provided with the Muse distribution,
+A copy of <a href="http://www.eclipse.org/equinox/" class="external">Eclipse Equinox</a> is provided with the Muse distribution,
and a target deployment environment for your plugin is created when the ant script executes. This environment is created
-by the <code>layout</code> target of the <code>build.xml</code>. If you would like to deploy your Bundle into a pre-existing
+by the <em>layout</em> target of the <em>build.xml</em> file. If you would like to deploy your Bundle into a pre-existing
equinox installation, you would simply need to ensure that your Bundle, along with the rest of the Bundles in the generated
target deployment environment, are available.
<p>
Modified: webservices/muse/site/docs/2.0.0/tutorial/08-test-client.html
URL: http://svn.apache.org/viewvc/webservices/muse/site/docs/2.0.0/tutorial/08-test-client.html?view=diff&rev=447446&r1=447445&r2=447446
==============================================================================
--- webservices/muse/site/docs/2.0.0/tutorial/08-test-client.html (original)
+++ webservices/muse/site/docs/2.0.0/tutorial/08-test-client.html Mon Sep 18 08:56:36 2006
@@ -109,17 +109,6 @@
<div id="content">
<div id="skinconf-txtlink"></div>
<h2>Apache Muse - Testing Your Application</h2>
-<div id="minitoc-area">
-<ul class="minitoc">
-<li>
-<a href="#Section1">Connecting to a Deployed Endpoint</a>
-</li>
-</ul>
-</div>
-
-<a name="N1000C"></a><a name="Section1"></a>
-<h2 class="boxed">Connecting to a Deployed Endpoint</h2>
-<div class="section">
<p>When communicating with a resource, you must create a client to that resource as described <a href="03-wsdl2java.html#Section4">earlier</a>.
After adding the generated client jar to your compilation classpath, you can create a client for the sample resource like so:
<code>
@@ -185,7 +174,6 @@
<p>Finally the <em>setTrace()</em> call will print all of the outgoing and incoming messages to standard output. This is extremely useful
when developing your endpoints. This operation is available on all generated clients, but the other methods will be specific to your
endpoint.</p>
-</div>
<p>
<br/>
<a href="07-deploy-application-axis2.html"><strong><</strong> Back (Axis2)</a>
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-commits-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-commits-help@ws.apache.org