Author: steveh
Date: Wed Mar 2 15:16:05 2005
New Revision: 155975
URL: http://svn.apache.org/viewcvs?view=rev&rev=155975
Log:
Fix for BEEHIVE-101: Control overview page missing links and typo
Other misc changes: update to AddressBookWS sample doc, livesite doc.
Modified:
incubator/beehive/site/build/site/controls/controlsOverview.html
incubator/beehive/site/src/documentation/content/xdocs/controls/controlsOverview.xml
incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsOverview.xml
incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/wsm/sample_AddressBook.xml
incubator/beehive/trunk/docs/updating_livesite.txt
Modified: incubator/beehive/site/build/site/controls/controlsOverview.html
URL:
http://svn.apache.org/viewcvs/incubator/beehive/site/build/site/controls/controlsOverview.html?view=diff&r1=155974&r2=155975
==============================================================================
--- incubator/beehive/site/build/site/controls/controlsOverview.html (original)
+++ incubator/beehive/site/build/site/controls/controlsOverview.html Wed Mar 2
15:16:05 2005
@@ -477,7 +477,7 @@
<strong>
-For existing client models, the configuration of resource access is often some
combination of resource-specific API usage and deployment descriptor entries.
This generally requires custom IDE code that is knows how to generate the right
(resource-specific) code or configuration entries.</strong>
+For existing client models, the configuration of resource access is often some
combination of resource-specific API usage and deployment descriptor entries.
This generally requires custom IDE code that knows how to generate the right
(resource-specific) code or configuration entries.</strong>
</p>
<p>Specific resource types often need custom code in order to define wizards
or property-driven user interface that aids in the process of defining a client
of the resource. There is no common mechanism for discovering the potential set
of configurable attributes for a resource type. This means that any graphical
presentation of client attributes or wizards must be custom-authored based upon
resource type.
Modified:
incubator/beehive/site/src/documentation/content/xdocs/controls/controlsOverview.xml
URL:
http://svn.apache.org/viewcvs/incubator/beehive/site/src/documentation/content/xdocs/controls/controlsOverview.xml?view=diff&r1=155974&r2=155975
==============================================================================
---
incubator/beehive/site/src/documentation/content/xdocs/controls/controlsOverview.xml
(original)
+++
incubator/beehive/site/src/documentation/content/xdocs/controls/controlsOverview.xml
Wed Mar 2 15:16:05 2005
@@ -97,7 +97,7 @@
<p>
<strong>
-For existing client models, the configuration of resource access is often some
combination of resource-specific API usage and deployment descriptor entries.
This generally requires custom IDE code that is knows how to generate the right
(resource-specific) code or configuration entries.</strong>
+For existing client models, the configuration of resource access is often some
combination of resource-specific API usage and deployment descriptor entries.
This generally requires custom IDE code that knows how to generate the right
(resource-specific) code or configuration entries.</strong>
</p>
<p>Specific resource types often need custom code in order to
define wizards or property-driven user interface that aids in the process of
defining a client of the resource. There is no common mechanism for discovering
the potential set of configurable attributes for a resource type. This means
that any graphical presentation of client attributes or wizards must be
custom-authored based upon resource type.
</p>
Modified:
incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsOverview.xml
URL:
http://svn.apache.org/viewcvs/incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsOverview.xml?view=diff&r1=155974&r2=155975
==============================================================================
---
incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsOverview.xml
(original)
+++
incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/controls/controlsOverview.xml
Wed Mar 2 15:16:05 2005
@@ -97,7 +97,7 @@
<p>
<strong>
-For existing client models, the configuration of resource access is often some
combination of resource-specific API usage and deployment descriptor entries.
This generally requires custom IDE code that is knows how to generate the right
(resource-specific) code or configuration entries.</strong>
+For existing client models, the configuration of resource access is often some
combination of resource-specific API usage and deployment descriptor entries.
This generally requires custom IDE code that knows how to generate the right
(resource-specific) code or configuration entries.</strong>
</p>
<p>Specific resource types often need custom code in order to
define wizards or property-driven user interface that aids in the process of
defining a client of the resource. There is no common mechanism for discovering
the potential set of configurable attributes for a resource type. This means
that any graphical presentation of client attributes or wizards must be
custom-authored based upon resource type.
</p>
Modified:
incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/wsm/sample_AddressBook.xml
URL:
http://svn.apache.org/viewcvs/incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/wsm/sample_AddressBook.xml?view=diff&r1=155974&r2=155975
==============================================================================
---
incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/wsm/sample_AddressBook.xml
(original)
+++
incubator/beehive/trunk/docs/forrest/src/documentation/content/xdocs/wsm/sample_AddressBook.xml
Wed Mar 2 15:16:05 2005
@@ -113,6 +113,7 @@
deploy.beehive.webapp.runtime
<strong>Copy and paste version:</strong>
+
ant -f %BEEHIVE_HOME%\ant\webappRuntimeCore.xml
-Dwebapp.dir=C:\beehive_projects\AddressBookWS
deploy.beehive.webapp.runtime</source>
<source>ant
-f %BEEHIVE_HOME%\ant\webappRuntimeCore.xml
@@ -120,6 +121,7 @@
deploy.beehive.webapp.runtime
<strong>Copy and paste version:</strong>
+
ant -f %BEEHIVE_HOME%\ant\webappRuntimeCore.xml
-Dwebapp.dir=C:\beehive_projects\EmployeeWS
deploy.beehive.webapp.runtime</source>
</section>
<section id="external_jars">
@@ -127,11 +129,11 @@
<p>Download the junit ZIP archive from <a
href="http://prdownloads.sourceforge.net/junit/junit3.8.1.zip?download";>http://prdownloads.sourceforge.net/junit/junit3.8.1.zip?download</a>
</p>
- <p>Unzip the archive and copy
<code>junit.jar</code> to
+ <p>Unzip the archive, locate
<code>junit.jar</code>, and copy <code>junit.jar</code> to
<code>ANT_HOME/lib</code>.</p>
<p> Download the derby ZIP archive from <a
href="http://incubator.apache.org/derby/binaries/derby_snapshot_svnversion_46005.ZIP";>http://incubator.apache.org/derby/binaries/derby_snapshot_svnversion_46005.ZIP</a>.</p>
- <p>Unzip the archive and copy
<code>derby.jar</code> to
+ <p>Unzip the archive, locate
<code>derby.jar</code>, and copy <code>derby.jar</code> to
<code>C:/beehive_projects/EmployeeWS/WEB-INF/lib</code>.</p>
</section>
<section id="compile">
@@ -143,6 +145,7 @@
build
<strong>Copy and paste version:</strong>
+
ant -f %BEEHIVE_HOME%\ant\buildWebapp.xml
-Dwebapp.dir=C:\beehive_projects\AddressBookWS build</source>
<p>To compile the EmployeeWS app, enter the following Ant
command:</p>
<source>ant
@@ -151,13 +154,14 @@
build
<strong>Copy and paste version:</strong>
+
ant -f %BEEHIVE_HOME%\ant\buildWebapp.xml
-Dwebapp.dir=C:\beehive_projects\EmployeeWS build</source>
- </section>
+ </section>
<section id="start_tomcat">
<title>To Start Tomcat</title>
<p>To start Tomcat, run the following
command:</p>
<source>%CATALINA_HOME%\bin\startup.bat</source>
- </section>
+ </section>
<section id="deploy">
<title>To Deploy to Tomcat</title>
<p>To deploy the applications, click the following links. We recommend
that you open the
@@ -207,15 +211,22 @@
http://localhost:8080/EmployeeWS/web/Service.jws?wsdl</a>
</p>
- </section>
-
+ </section>
</section>
<section id="setup_clients">
- <title>To Set up the Clients</title>
- <p>To generate the clients run the following
build files.</p>
-<source>ant -f
C:/beehive_projects/AddressBookWS/WEB-INF/build-client.xml</source>
+ <title>To Run the Web Service Clients</title>
+ <p>Open the following two build files.</p>
+
<source>C:\beehive_projects\AddressBookWS\WEB-INF\build-client-dist.xml</source>
+
<source>C:\beehive_projects\EmployeeWS\WEB-INF\build-client-dist.xml</source>
+ <p>In each file, edit the following line</p>
+ <source> <import
file="../../../beehive-imports.xml" /></source>
+ <p>so that it points to the
+ <code>beehive-import.xml</code> file,
for example:</p>
+ <source> <import
file="C:/apache/apache-beehive-incubating-svn-snapshot/beehive-imports.xml"
/></source>
+ <p>To generate and run the clients run the
following build files.</p>
+<source>ant -f
C:/beehive_projects/AddressBookWS/WEB-INF/build-client-dist.xml</source>
<p>and</p>
-<source>ant -f C:/beehive_projects/EmployeeWS/WEB-INF/build-client.xml</source>
+<source>ant -f
C:/beehive_projects/EmployeeWS/WEB-INF/build-client-dist.xml</source>
<p>Note that you do not need to run a
particular target within
<code>client-build.xml</code>. Simply
run the ant commands
shown above and the client will be
generated in
Modified: incubator/beehive/trunk/docs/updating_livesite.txt
URL:
http://svn.apache.org/viewcvs/incubator/beehive/trunk/docs/updating_livesite.txt?view=diff&r1=155974&r2=155975
==============================================================================
--- incubator/beehive/trunk/docs/updating_livesite.txt (original)
+++ incubator/beehive/trunk/docs/updating_livesite.txt Wed Mar 2 15:16:05 2005
@@ -61,9 +61,9 @@
This will build a ZIP file called "site.zip" and save it at
- /beehive/trunk/build/jars/site.zip
+ /beehive/trunk/build/dist/archives/site.zip
-Note: this ZIP file has no top-level directory. If you unzip it, it will
+Note: this ZIP file has *no* top-level directory. If you unzip it, it will
spew files all over the directory you unzip it into. For this reason, you
should
take care where you unzip it.
