You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wookie.apache.org by bu...@apache.org on 2012/07/06 16:36:55 UTC
svn commit: r824815 - in /websites/staging/wookie/trunk/content: ./
wookie/docs/developer/release-management.html
wookie/docs/developer/running.html wookie/news.html
Author: buildbot
Date: Fri Jul 6 14:36:55 2012
New Revision: 824815
Log:
Staging update by buildbot for wookie
Modified:
websites/staging/wookie/trunk/content/ (props changed)
websites/staging/wookie/trunk/content/wookie/docs/developer/release-management.html
websites/staging/wookie/trunk/content/wookie/docs/developer/running.html
websites/staging/wookie/trunk/content/wookie/news.html
Propchange: websites/staging/wookie/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jul 6 14:36:55 2012
@@ -1 +1 @@
-1352842
+1358242
Modified: websites/staging/wookie/trunk/content/wookie/docs/developer/release-management.html
==============================================================================
--- websites/staging/wookie/trunk/content/wookie/docs/developer/release-management.html (original)
+++ websites/staging/wookie/trunk/content/wookie/docs/developer/release-management.html Fri Jul 6 14:36:55 2012
@@ -86,7 +86,7 @@ In addition to Nexus, a source and stand
<h3 id="apache-wookie-incubating-release-guidelines">Apache Wookie (Incubating) Release Guidelines</h3>
<ol>
<li><a href="/wookie/docs/developer/release-configuration.html">Release Manager Configuration Guide</a></li>
-<li><a href="/wookie/docs/developer/release-overview.html">Release overview</a></li>
+<li><a href="/wookie/docs/developer/release-overview.html">Release Overview</a></li>
<li><a href="/wookie/docs/developer/release-process.html">Release Process</a></li>
<li><a href="/wookie/docs/developer/release-testing.html">Release Testing</a></li>
</ol>
Modified: websites/staging/wookie/trunk/content/wookie/docs/developer/running.html
==============================================================================
--- websites/staging/wookie/trunk/content/wookie/docs/developer/running.html (original)
+++ websites/staging/wookie/trunk/content/wookie/docs/developer/running.html Fri Jul 6 14:36:55 2012
@@ -64,6 +64,7 @@
<li><a href="/wookie/docs/developer/features.html">Extension Features</a></li>
<li><a href="/wookie/docs/developer/widgets.html">Deploying Widgets</a></li>
<li><a href="/wookie/docs/develop.html">Environment</a></li>
+<li><a href="/wookie/docs/developer/release-management.html">Release Management</a></li>
<li><a href="/wookie/docs/developer/issues.html">Issue Tracker</a></li>
<li><a href="/wookie/docs/developer/index.html">Management</a></li>
<li><a href="/wookie/docs/developer/parser.html">W3C Widget Parser</a></li>
@@ -78,8 +79,8 @@
</div>
<div id="content">
- <p>This page documents the various ways of running Wookie.</p>
-<h2 id="running_wookie_in_standalone_mode">Running Wookie in "standalone" mode</h2>
+ <p>This page documents the various ways of running Wookie. See also the <a href="../admin.html">Server Administration</a> documentation for more details on initial server configuration such as security settings.</p>
+<h2 id="running-wookie-in-standalone-mode">Running Wookie in "standalone" mode</h2>
<p>The quickest way to run Wookie is in "standalone" mode; in this mode Wookie uses a local database and embedded server. This is a good way to experiment with Wookie in development.</p>
<p>To run Wookie in standalone mode:</p>
<div class="codehilite"><pre><span class="n">cd</span> <span class="n">PROJECT_HOME_DIRECTORY</span>
@@ -91,14 +92,15 @@
<p>Note that by default, wookie will clean the database each time it is run, this ensures that your development environment starts in a consistent state. However, any modifications you have made to the database during previous runs will be lost.</p>
<p>To run the development server without cleaning the database you need to set initDB=false. See the next section for more details.</p>
<p>Once the server is running go to http://localhost:8080/wookie</p>
-<p>To access the administration menu (http://localhost:8080/wookie/admin) use the username 'java' and password 'java'.</p>
<p>If you want to start with a completely clean build then use:</p>
<div class="codehilite"><pre><span class="n">cd</span> <span class="n">PROJECT_HOME_DIRECTORY</span>
<span class="n">ant</span> <span class="n">clean</span><span class="o">-</span><span class="n">build</span> <span class="n">run</span>
</pre></div>
-<h3 id="running_options">Running options</h3>
+<p>Note that running in standalone mode uses a number of defaults, including a default admin user name and password, and a default API key, all of
+which should be changed on a server that is publicly available; see the <a href="../admin.html">Server Administration</a> guide for more details.</p>
+<h3 id="running-options">Running options</h3>
<p>To set run mode options you can either add properties to the local.build.properties file or you can pass properties in via the command line using -Drun.args="<property_name>=<property_value> <property_name>=<property_value>". For example:</p>
<div class="codehilite"><pre><span class="o">-</span><span class="n">Drun</span><span class="o">.</span><span class="n">args</span><span class="o">=</span><span class="s">"port=8080 initDB=false"</span>
</pre></div>
@@ -126,7 +128,7 @@
</tr>
</tbody></table>
-<h2 id="running_wookie_with_tomcat_and_mysql">Running Wookie with Tomcat and MySQL</h2>
+<h2 id="running-wookie-with-tomcat-and-mysql">Running Wookie with Tomcat and MySQL</h2>
<p>The following will compile and run the server in Tomcat with a specified RDBMS using JPA persistence. The database schema can be defined and populated on launch, however you must have previously done the following:</p>
<ol>
<li>Obtained a JDBC driver jar file for the database,</li>
@@ -193,6 +195,7 @@ jar archive.</p>
</pre></div>
+<p>(Where "java" is your own admin username and password. See also the <a href="../admin.html">server administration</a> guide for other security information)</p>
<p>If you have previously used Wookie in standalone deployment, to ensure the right scripts are included in the build you need to run:</p>
<div class="codehilite"><pre><span class="n">ant</span> <span class="n">clean</span><span class="o">-</span><span class="n">build</span>
</pre></div>
@@ -210,7 +213,7 @@ jar archive.</p>
</pre></div>
-<h2 id="running_wookie_with_a_security_manager">Running Wookie with a security manager</h2>
+<h2 id="running-wookie-with-a-security-manager">Running Wookie with a security manager</h2>
<p><strong><em>NOTE: This section was written before moving from Hibernate to OpenJPA/JCR and so some of these instructions may no longer be correct.</em></strong></p>
<p>If you are running Wookie with a security manager you will have to grant some permissions to get Wookie running properly. Otherwise you are likely to run into this of a similar error:</p>
<div class="codehilite"><pre><span class="err">SEVERE:</span> <span class="err">Exception</span> <span class="err">sending</span> <span class="err">context</span> <span class="err">initialized</span> <span class="err">event</span> <span class="err">to</span> <span class="err">listener</span> <span class="err">instance</span> <span class="err">of</span> <span class="kd">class</span> <span class="nc">org.apache.wookie.server.ContextListener</span>
@@ -263,7 +266,7 @@ jar archive.</p>
are really concerned to limit permissions as much as possible, you need to define
stricter rules, but it's a start and should get your Wookie instance up-and-running.</p>
<p>For more information how to do this in Tomcat, see the <a href="http://tomcat.apache.org/tomcat-6.0-doc/security-manager-howto.html">Tomcat Security Manager HOW-TO</a></p>
-<h2 id="running_wookie_using_embedded_jackrabbit_jcr">Running Wookie using embedded Jackrabbit JCR</h2>
+<h2 id="running-wookie-using-embedded-jackrabbit-jcr">Running Wookie using embedded Jackrabbit JCR</h2>
<p>Wookie by default uses OpenJPA for persistence, however you can also use JCR. This is not part of the standard build and distribution of Wookie, so first you need to build the module, then include it in Wookie's dependencies.</p>
<p>The first step is to build and publish the core Wookie server code, as the JCR module build process depends on being able to find it using Ivy. </p>
<div class="codehilite"><pre><span class="n">cd</span> <span class="n">PROJECT</span><span class="o">-</span><span class="n">HOME</span><span class="o">-</span><span class="n">DIRECTORY</span>
@@ -292,11 +295,11 @@ stricter rules, but it's a start and sho
<p>These replace the wookie.db.* and jdbc.drive.path settings above, but otherwise the instructions apply for the JCR configuration.</p>
-<h2 id="running_wookie_with_other_configurations">Running Wookie with other configurations</h2>
+<h2 id="running-wookie-with-other-configurations">Running Wookie with other configurations</h2>
<p>Other configurations of Wookie can also be run; the main requirements are a servlet container and a database.</p>
<p>Database connections can be set up using either JPA (Java Persistence API) or JCR; the configuration details are set in build.properties. Additional configuration for advanced use can be found in org.apache.wookie.beans.jpa/peristence.properties. The database schema and mappings is located in etc/ddl-schema.</p>
<p>The deploy-webapp task can be used to deploy Wookie to any servlet container application.</p>
-<h2 id="running_wookie_in_a_virtual_host_configuration">Running Wookie in a virtual host configuration</h2>
+<h2 id="running-wookie-in-a-virtual-host-configuration">Running Wookie in a virtual host configuration</h2>
<p>To run Wookie using a virtual host configuration - for example, to run Wookie on http://localhost:8080/wookie,
but with the external URL http://my.wookie.org/wookie - you need to set the following properties in widgetserver.properties or local.widgetserver.properties:</p>
<div class="codehilite"><pre> <span class="n">widget</span><span class="o">.</span><span class="n">server</span><span class="o">.</span><span class="n">scheme</span><span class="o">=</span><span class="n">http</span>
Modified: websites/staging/wookie/trunk/content/wookie/news.html
==============================================================================
--- websites/staging/wookie/trunk/content/wookie/news.html (original)
+++ websites/staging/wookie/trunk/content/wookie/news.html Fri Jul 6 14:36:55 2012
@@ -83,7 +83,7 @@
<p><em>22 June 2012</em></p>
<p>We're pleased to announce the release of Apache Wookie 0.11.0 (incubating)! This is the fifth release,
and contains a revamp in the codebase, removing a lot of redundancy in the core code as well as adding new
-features for widget using the Wave feature.</p>
+features for widgets using the Wave feature.</p>
<p>For more information on 0.11.0 see the <a href="docs/releases/0p11p0.html">New and Noteworthy</a> page.</p>
<p>Download the new release from the <a href="docs/download.html">download and quickstart</a> page.</p>
<h1 id="wookie-0100-released">Wookie 0.10.0 released!</h1>