geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r917744 [21/31] - in /websites/production/geronimo/content: GMOxDOC20/ GMOxDOC20/geronimo-eclipse-plugin-installation-instructions.data/ cache/
Date Tue, 29 Jul 2014 00:52:21 GMT
Modified: websites/production/geronimo/content/GMOxDOC20/multiple-repositories.html
==============================================================================
--- websites/production/geronimo/content/GMOxDOC20/multiple-repositories.html (original)
+++ websites/production/geronimo/content/GMOxDOC20/multiple-repositories.html Tue Jul 29 00:52:18
2014
@@ -23,6 +23,7 @@
   <script src='http://geronimo.apache.org/resources/highlighter/scripts/shCore.js' type='text/javascript'></script>
   <script src='http://geronimo.apache.org/resources/highlighter/scripts/shBrushJava.js'
type='text/javascript'></script>
   <script src='http://geronimo.apache.org/resources/highlighter/scripts/shBrushXml.js'
type='text/javascript'></script>
+  <script src='http://geronimo.apache.org/resources/highlighter/scripts/shBrushPlain.js'
type='text/javascript'></script>
   
   <script type="text/javascript">
   SyntaxHighlighter.defaults['toolbar'] = false;
@@ -95,15 +96,26 @@
 
       <div class="pagecontent">
         <div class="wiki-content">
-          <div class="wiki-content maincontent"><style type="text/css">/*<![CDATA[*/
-table.ScrollbarTable  {border: none;padding: 3px;width: 100%;padding: 3px;margin: 0px;background-color:
#f0f0f0}
-table.ScrollbarTable td.ScrollbarPrevIcon {text-align: center;width: 16px;border: none;}
-table.ScrollbarTable td.ScrollbarPrevName {text-align: left;border: none;}
-table.ScrollbarTable td.ScrollbarParent {text-align: center;border: none;}
-table.ScrollbarTable td.ScrollbarNextName {text-align: right;border: none;}
-table.ScrollbarTable td.ScrollbarNextIcon {text-align: center;width: 16px;border: none;}
+          <div class="wiki-content maincontent">    
+<div class="atb-scrollbar-macro">
+    <div class="prev">
+        
+    </div>
+    <div class="parent">
+                    <a shape="rect" href="running-geronimo.html" rel="parent">
+                                            <span class="aui-icon aui-icon-small atb-icon-arrow-up">Up</span>
+                                        <span class="title">Running Geronimo</span>
+                </a>
+
+            </div>
+    <div class="next">
+        <a shape="rect" href="running-geronimo-as-a-non-root-user.html" rel="next">
+                <span class="title">Running Geronimo as a non-root user</span>
+                                    <span class="aui-icon aui-icon-small atb-icon-arrow-right">Next</span>
+                            </a>
 
-/*]]>*/</style><div class="Scrollbar"><table class="ScrollbarTable"><tr><td
colspan="1" rowspan="1" class="ScrollbarPrevName" width="33%">&#160;</td><td
colspan="1" rowspan="1" class="ScrollbarParent" width="33%"><sup><a shape="rect"
href="running-geronimo.html"><img align="middle" border="0" src="https://cwiki.apache.org/confluence/images/icons/up_16.gif"
width="8" height="8"></a></sup><a shape="rect" href="running-geronimo.html">Running
Geronimo</a></td><td colspan="1" rowspan="1" class="ScrollbarNextName" width="33%">&#160;<a
shape="rect" href="running-geronimo-as-a-non-root-user.html">Running Geronimo as a non-root
user</a></td><td colspan="1" rowspan="1" class="ScrollbarNextIcon"><a
shape="rect" href="running-geronimo-as-a-non-root-user.html"><img align="middle" border="0"
src="https://cwiki.apache.org/confluence/images/icons/forwd_16.gif" width="16" height="16"></a></td></tr></table></div>
+    </div>
+</div>
 <p>This article applies to Geronimo 2.0 and later.</p>
 
 <p>This article describes running multiple server instances from one installation instance
of Geronimo, where the server instances share as much of the base Geronimo artifacts and file
system space as possible.  These are the geronimo directories, all sub-directories of &lt;geronimo_home&gt;
by default:</p>
@@ -114,7 +126,7 @@ table.ScrollbarTable td.ScrollbarNextIco
 
 <p>In addition to a simple read/write partition of capabilities, security may well
come into play as we access permissions on a set of directories. Each server instance should
be able to read or write only its var directory, for instance.</p>
 
-<h2><a shape="rect" name="MultipleRepositories-ConfigurationSubstitutionProperties"></a>Configuration
Substitution Properties</h2>
+<h2 id="MultipleRepositories-ConfigurationSubstitutionProperties">Configuration Substitution
Properties</h2>
 
 <p>A feature that helps with running multiple servers, whether or not they are sharing
a repository, is the configuration substitution property facility.  config.xml can have expressions
of the form </p>
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
@@ -128,28 +140,28 @@ These override each other in the order a
 
 
 
-<h2><a shape="rect" name="MultipleRepositories-MultipleServerInstances"></a>Multiple
Server Instances</h2>
+<h2 id="MultipleRepositories-MultipleServerInstances">Multiple Server Instances</h2>
 
 <p>A server instance is easy to create in Geronimo:</p>
-<ol><li>Set the <tt>org.apache.geronimo.server.name</tt> system property
to the instance name before you start the server.
-	<ul><li>Use the syntax <tt>-Dorg.apache.geronimo.server.name=foo</tt>
to name your instance <tt>foo</tt>.</li><li>There are two ways to
do this:
-		<ol><li>Add this to your <tt>GERONIMO_OPTS</tt> environment variable,
or</li><li>Pass it on the java command-line invocation of the server.</li></ol>
-		</li><li>This server's var and deploy directory will then be under <tt>&lt;geronimo_home&gt;/foo</tt>.</li><li><tt>org.apache.geronimo.server.name</tt>
may be any pathname relative to (descending from) &lt;geronimo_home&gt;.  For example,
<tt>servers/bar</tt> would put the server's var directory under <tt>&lt;geronimo_home&gt;/servers/bar</tt>.</li><li>The
<tt>org.apache.geronimo.server.dir</tt> system property may also be used, and
it overrides <tt>org.apache.geronimo.server.name</tt>.</li><li>Use
<tt>org.apache.geronimo.server.dir</tt> to specify an absolute path, which need
not be relative to &lt;geronimo_home&gt;. For example, <tt>/ag20/servers/bar</tt>
would put the server's var directory under <tt>/ag20/servers/bar</tt>.  Otherwise,
the two system properties behave the same.</li></ul>
-	</li><li><tt><b>mkdir foo</b></tt></li><li>Copy
var/* to foo/var/</li><li>Edit <tt>foo/var/config/config-substitutions.properties</tt>,
uncomment <tt>PortOffset</tt> and change it to a value like <tt>1,2,10,11,12,20,21,22,...</tt>
so the ports in the new server instance will not conflict with existing server instances you
already have defined and/or started. (Alternatively start the server with the property -Dorg.apache.geronimo.config.substitution.PortOffset=3
in the command line)</li><li>Start the server.</li></ol>
+<ol><li>Set the <code>org.apache.geronimo.server.name</code> system
property to the instance name before you start the server.
+	<ul><li>Use the syntax <code>-Dorg.apache.geronimo.server.name=foo</code>
to name your instance <code>foo</code>.</li><li>There are two ways
to do this:
+		<ol><li>Add this to your <code>GERONIMO_OPTS</code> environment
variable, or</li><li>Pass it on the java command-line invocation of the server.</li></ol>
+		</li><li>This server's var and deploy directory will then be under <code>&lt;geronimo_home&gt;/foo</code>.</li><li><code>org.apache.geronimo.server.name</code>
may be any pathname relative to (descending from) &lt;geronimo_home&gt;.  For example,
<code>servers/bar</code> would put the server's var directory under <code>&lt;geronimo_home&gt;/servers/bar</code>.</li><li>The
<code>org.apache.geronimo.server.dir</code> system property may also be used,
and it overrides <code>org.apache.geronimo.server.name</code>.</li><li>Use
<code>org.apache.geronimo.server.dir</code> to specify an absolute path, which
need not be relative to &lt;geronimo_home&gt;. For example, <code>/ag20/servers/bar</code>
would put the server's var directory under <code>/ag20/servers/bar</code>.  Otherwise,
the two system properties behave the same.</li></ul>
+	</li><li><code><strong>mkdir foo</strong></code></li><li>Copy
var/* to foo/var/</li><li>Edit <code>foo/var/config/config-substitutions.properties</code>,
uncomment <code>PortOffset</code> and change it to a value like <code>1,2,10,11,12,20,21,22,...</code>
so the ports in the new server instance will not conflict with existing server instances you
already have defined and/or started. (Alternatively start the server with the property -Dorg.apache.geronimo.config.substitution.PortOffset=3
in the command line)</li><li>Start the server.</li></ol>
 
 
 <p>To deploy applications to the new server instance, you need to specify the NamingPort+PortOffset
used, such as for PortOffset=1:</p>
 <ul><li>deploy -port 1100 list-modules</li></ul>
 
 
-<h2><a shape="rect" name="MultipleRepositories-MultipleRepositories"></a>Multiple
Repositories</h2>
+<h2 id="MultipleRepositories-MultipleRepositories">Multiple Repositories</h2>
 
 <p>First, we consider the single server instance case, and just add a second repository.
Say we want to leave Geronimo in its repository, but add a second repository to deploy our
applications. Adding a second repository is pretty easy.</p>
 <ol><li>Create a plan (say repo2.xml) for your repository module.
-<div class="code panel" style="border-style: solid;border-width: 1px;"><div class="codeHeader
panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>repo2.xml</b></div><div
class="codeContent panelContent">
+<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div
class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>repo2.xml</b></div><div
class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;module xmlns="http://geronimo.apache.org/xml/ns/deployment-1.2"&gt;
+&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+&lt;module xmlns=&quot;http://geronimo.apache.org/xml/ns/deployment-1.2&quot;&gt;
   &lt;environment&gt;
     &lt;moduleId&gt;
       &lt;groupId&gt;org.example.configs&lt;/groupId&gt;
@@ -169,53 +181,88 @@ These override each other in the order a
     &lt;non-overridable-classes/&gt;
   &lt;/environment&gt;
   &lt;!--Repository--&gt;
-  &lt;gbean name="Repo2" class="org.apache.geronimo.system.repository.Maven2Repository"&gt;
-    &lt;attribute name="root"&gt;repo2s/&lt;/attribute&gt;
-    &lt;attribute name="resolveToServer"&gt;true&lt;/attribute&gt;
-    &lt;reference name="ServerInfo"&gt;
+  &lt;gbean name=&quot;Repo2&quot; class=&quot;org.apache.geronimo.system.repository.Maven2Repository&quot;&gt;
+    &lt;attribute name=&quot;root&quot;&gt;repo2s/&lt;/attribute&gt;
+    &lt;attribute name=&quot;resolveToServer&quot;&gt;true&lt;/attribute&gt;
+    &lt;reference name=&quot;ServerInfo&quot;&gt;
       &lt;name&gt;ServerInfo&lt;/name&gt;
     &lt;/reference&gt;
   &lt;/gbean&gt;
   &lt;!--Configuration Store service--&gt;
-  &lt;gbean name="Local2" class="org.apache.geronimo.system.configuration.RepositoryConfigurationStore"&gt;
-    &lt;reference name="Repository"&gt;
+  &lt;gbean name=&quot;Local2&quot; class=&quot;org.apache.geronimo.system.configuration.RepositoryConfigurationStore&quot;&gt;
+    &lt;reference name=&quot;Repository&quot;&gt;
       &lt;name&gt;Repo2&lt;/name&gt;
     &lt;/reference&gt;
   &lt;/gbean&gt;
 &lt;/module&gt;
 ]]></script>
-</div></div></li><li>Create the repository's root directory via <tt><b>mkdir
&lt;geronimo_home&gt;/repo2s</b></tt>
-	<ul><li>The directory is specified by the <tt>root</tt> attribute
of the Maven2Repository GBean, <tt>repo2s/</tt> in the above example. It is a
path relative to the base directory &lt;geronimo_home&gt;.</li><li>The
<tt>resolveToServer</tt> attribute specifies the repository's location.
-		<ul><li><tt>true</tt> means this path is relative to baseServer,
which is useful with multiple server instances.</li><li><tt>false</tt>
means this path is relative to the base directory &lt;geronimo_home&gt;.</li></ul>
+</div></div></li><li>Create the repository's root directory via <code><strong>mkdir
&lt;geronimo_home&gt;/repo2s</strong></code>
+	<ul><li>The directory is specified by the <code>root</code> attribute
of the Maven2Repository GBean, <code>repo2s/</code> in the above example. It is
a path relative to the base directory &lt;geronimo_home&gt;.</li><li>The
<code>resolveToServer</code> attribute specifies the repository's location.
+		<ul><li><code>true</code> means this path is relative to baseServer,
which is useful with multiple server instances.</li><li><code>false</code>
means this path is relative to the base directory &lt;geronimo_home&gt;.</li></ul>
 		</li></ul>
-	</li><li>Deploy the repository module by deploying <tt>repo2.xml</tt>
via <b><tt>deploy deploy repo2.xml</tt></b>.
-<div class="panelMacro"><table class="tipMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif"
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">The
<b><tt>deploy</tt></b> command is the script &lt;geronimo_home&gt;/bin/deploy.{bat,sh},
depending on your operating system.  It is invoked by typing simply <tt>deploy</tt>
either from the &lt;geronimo_home&gt;/bin directory, or by having that directory in
your path.</td></tr></table></div></li></ol>
+	</li><li>Deploy the repository module by deploying <code>repo2.xml</code>
via <strong><code>deploy deploy repo2.xml</code></strong>.
+    <div class="aui-message success shadowed information-macro">
+                            <span class="aui-icon icon-success">Icon</span>
+                <div class="message-content">
+                            <p>The <strong><code>deploy</code></strong>
command is the script &lt;geronimo_home&gt;/bin/deploy.{bat,sh}, depending on your
operating system.  It is invoked by typing simply <code>deploy</code> either from
the &lt;geronimo_home&gt;/bin directory, or by having that directory in your path.</p>
+                    </div>
+    </div>
+</li></ol>
+
+
+<h3 id="MultipleRepositories-Usingthenewrepository">Using the new repository</h3>
 
+<p>Using the new repository is a little tricky, and is only supported from the command
line currently.  The essence is to use the <code>--targets</code> option of the
<code><strong>deploy</strong></code> command to target your module
to deploy in your new repository.  First, use the deployer list-targets command to see the
repositories. The target names are long and cumbersome:</p>
 
-<h3><a shape="rect" name="MultipleRepositories-Usingthenewrepository"></a>Using
the new repository</h3>
+<p><code><strong>deploy list-targets</strong></code></p>
 
-<p>Using the new repository is a little tricky, and is only supported from the command
line currently.  The essence is to use the <tt>--targets</tt> option of the <tt><b>deploy</b></tt>
command to target your module to deploy in your new repository.  First, use the deployer list-targets
command to see the repositories. The target names are long and cumbersome:</p>
+<p><code>Available Targets:</code><br clear="none">
+<code>org.example.configs/myrepo/2.0-SNAPSHOT/car?ServiceModule=org.example.configs/myrepo/2.0-SNAPSHOT/car,j2eeType=ConfigurationStore,name=Local2</code><br
clear="none">
+<code>org.apache.geronimo.configs/j2ee-system/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0-SNAPSHOT/car,j2eeType=ConfigurationStore,name=Local</code></p>
+    <div class="aui-message success shadowed information-macro">
+                            <span class="aui-icon icon-success">Icon</span>
+                <div class="message-content">
+                            <p>The use of environment variables is recommended for
command-line use. For example, <code><strong>set REPO2= org.example.configs/myrepo/2.0-SNAPSHOT/car?ServiceModule=org.example.configs/myrepo/2.0-SNAPSHOT/car,j2eeType=ConfigurationStore,name=Local2</strong></code>.</p>
+                    </div>
+    </div>
+
+<p>To deploy to the new repository, use: <code><strong>deploy deploy --targets
%REPO2% sample.war</strong></code></p>
+
+<p><code><strong>deploy list-modules</strong></code> also gives
those long target names for each repo, followed by the usual short names of each module deployed
in the repo.<br clear="none">
+<code><strong>deploy list-modules %REPO2%</strong></code> gives the
accustomed short output for the target repo.</p>
 
-<p><tt><b>deploy list-targets</b></tt></p>
+<p>The syntax to undeploy from a repo is: <code><strong>deploy undeploy
"%REPO2%|geronimo/jsp-examples/1.1.1/war"</strong></code>.</p>
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            <p>Note the | character separates the repository name from
the module name.  The " quotes are used around the entire parameter to escape this special
character from command shell interpretation.</p>
+                    </div>
+    </div>
 
-<p><tt>Available Targets:</tt><br clear="none">
-<tt>org.example.configs/myrepo/2.0-SNAPSHOT/car?ServiceModule=org.example.configs/myrepo/2.0-SNAPSHOT/car,j2eeType=ConfigurationStore,name=Local2</tt><br
clear="none">
-<tt>org.apache.geronimo.configs/j2ee-system/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0-SNAPSHOT/car,j2eeType=ConfigurationStore,name=Local</tt></p>
-<div class="panelMacro"><table class="tipMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif"
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">The
use of environment variables is recommended for command-line use. For example, <tt><b>set
REPO2= org.example.configs/myrepo/2.0-SNAPSHOT/car?ServiceModule=org.example.configs/myrepo/2.0-SNAPSHOT/car,j2eeType=ConfigurationStore,name=Local2</b></tt>.</td></tr></table></div>
-<p>To deploy to the new repository, use: <tt><b>deploy deploy --targets
%REPO2% sample.war</b></tt></p>
+    <div class="aui-message problem shadowed information-macro">
+                            <span class="aui-icon icon-problem">Icon</span>
+                <div class="message-content">
+                            <p>If no <code>--targets</code> are given on
the deploy command, the module is deployed to all repositories. This certainly seems undesirable.
If you only want to put the module in one repository, be sure to use the <code>--targets</code>
option!</p>
+                    </div>
+    </div>
 
-<p><tt><b>deploy list-modules</b></tt> also gives those long
target names for each repo, followed by the usual short names of each module deployed in the
repo.<br clear="none">
-<tt><b>deploy list-modules %REPO2%</b></tt> gives the accustomed
short output for the target repo.</p>
 
-<p>The syntax to undeploy from a repo is: <tt><b>deploy undeploy "%REPO2%|geronimo/jsp-examples/1.1.1/war"</b></tt>.</p>
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif"
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">Note
the | character separates the repository name from the module name.  The " quotes are used
around the entire parameter to escape this special character from command shell interpretation.</td></tr></table></div>
-<div class="panelMacro"><table class="warningMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif"
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">If
no <tt>--targets</tt> are given on the deploy command, the module is deployed
to all repositories. This certainly seems undesirable. If you only want to put the module
in one repository, be sure to use the <tt>--targets</tt> option!</td></tr></table></div>
+<h3 id="MultipleRepositories-MultipleServerInstances,eachwithitsownrepository(ies)">Multiple
Server Instances, each with its own repository(ies)</h3>
 
-<h3><a shape="rect" name="MultipleRepositories-MultipleServerInstances%2Ceachwithitsownrepository%28ies%29"></a>Multiple
Server Instances, each with its own repository(ies)</h3>
+<p>In the case of multiple server instances, a separate path may be given for the Maven2Repository
root attribute for each server. This might be done with <code>config.xml</code>
overrides for each server instance.  A better solution is to add a <code>resolveToServer</code>
attribute to this GBean, so that the <code>root</code> attribute may be set to
<code>repository</code>, and it will thus be unique for each server instance with
no changes required for each instance.  Each server instance would then have a repository
located at <code>&lt;geronimo_home&gt;/&lt;instance_name&gt;/repository</code>.</p>
+    <div class="aui-message problem shadowed information-macro">
+                            <span class="aui-icon icon-problem">Icon</span>
+                <div class="message-content">
+                            <p>What's lacking is console support for multiple repositories,
and support for hot deployment and plugins.</p>
+                    </div>
+    </div>
 
-<p>In the case of multiple server instances, a separate path may be given for the Maven2Repository
root attribute for each server. This might be done with <tt>config.xml</tt> overrides
for each server instance.  A better solution is to add a <tt>resolveToServer</tt>
attribute to this GBean, so that the <tt>root</tt> attribute may be set to <tt>repository</tt>,
and it will thus be unique for each server instance with no changes required for each instance.
 Each server instance would then have a repository located at <tt>&lt;geronimo_home&gt;/&lt;instance_name&gt;/repository</tt>.</p>
-<div class="panelMacro"><table class="warningMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif"
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">What's
lacking is console support for multiple repositories, and support for hot deployment and plugins.</td></tr></table></div>
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif"
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">An
interesting wrinkle here is in what repository is the new repository deployed? It's clear
that the second repository (say <tt>repo2.xml</tt> above) <b>will</b>
be deployed in the first repository. Thus, making this first repository read-only will not
work for dynamically adding repositories. Perhaps a second repository is added to contain
these server-unique repositories. The second repository must be shared and read-write, so
it does not fit nicely in the use case. <img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/sad.gif"
height="20" width="20" alt="" border="0"></td></tr></table></div></div>
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            <p>An interesting wrinkle here is in what repository is
the new repository deployed? It's clear that the second repository (say <code>repo2.xml</code>
above) <strong>will</strong> be deployed in the first repository. Thus, making
this first repository read-only will not work for dynamically adding repositories. Perhaps
a second repository is added to contain these server-unique repositories. The second repository
must be shared and read-write, so it does not fit nicely in the use case. <img class="emoticon
emoticon-sad" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/sad.png"
data-emoticon-name="sad" alt="(sad)"></p>
+                    </div>
+    </div></div>
         </div>
 
         

Modified: websites/production/geronimo/content/GMOxDOC20/no-show.html
==============================================================================
--- websites/production/geronimo/content/GMOxDOC20/no-show.html (original)
+++ websites/production/geronimo/content/GMOxDOC20/no-show.html Tue Jul 29 00:52:18 2014
@@ -85,7 +85,7 @@
 
       <div class="pagecontent">
         <div class="wiki-content">
-          <div class="wiki-content maincontent"><ul><li><a shape="rect"
href="inbound-jca-adapter.html" title="Inbound JCA Adapter">Inbound JCA Adapter</a></li></ul></div>
+          <div class="wiki-content maincontent"><ul class="childpages-macro"><li><a
shape="rect" href="inbound-jca-adapter.html">Inbound JCA Adapter</a></li></ul></div>
         </div>
 
                   <div class="tabletitle">



Mime
View raw message