Author: buildbot
Date: Sun Mar 13 17:32:16 2016
New Revision: 982659
Log:
Staging update by buildbot for openwebbeans
Modified:
websites/staging/openwebbeans/trunk/content/ (props changed)
websites/staging/openwebbeans/trunk/content/owbconfig.html
Propchange: websites/staging/openwebbeans/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Mar 13 17:32:16 2016
@@ -1 +1 @@
-1734823
+1734828
Modified: websites/staging/openwebbeans/trunk/content/owbconfig.html
==============================================================================
--- websites/staging/openwebbeans/trunk/content/owbconfig.html (original)
+++ websites/staging/openwebbeans/trunk/content/owbconfig.html Sun Mar 13
17:32:16 2016
@@ -84,7 +84,63 @@ h2:hover > .headerlink, h3:hover > .head
<p>All those files contain at single property
<code>configuration.ordinal</code> which defines their
'importance'. Any setting from a property file with a higher
configuration.ordinal will
overwrite settings from one with a lower configuration.ordinal. The internally
used
-configuration.ordinal values range from 1 to 100.</p>
+configuration.ordinal values range from 1 to 100. The default value is 100.</p>
+<p>This trick allows us to split OpenWebBeans in different modules which
automatically change the container
+configuration if you put that jar on the classpath.</p>
+<p>For overriding the default configuration with own settings simply put a
<code>META-INF/openwebbeans/openwebbeans.properties</code>
+file into your projects classpath (e.g. into a jar) and either use a
<code>configuration.ordinal</code> higher than 100 or leave
+it empty to get the default value of 100.</p>
+<p>If you use OpenWebBeans as part of another project then you can assume that
most of the values got tweaked
+by the integration regarding to the specific needs.</p>
+<h2 id="configure-spi-implementations">Configure SPI implementations<a
class="headerlink" href="#configure-spi-implementations" title="Permanent
link">¶</a></h2>
+<p>OpenWebBeans provide a set of Service Provider Interfaces and multiple
different implementations a user can choose from.</p>
+<p>You can choose the implementations you like to use for your situation by
configuring them in
+<code>META-INF/openwebbeans/openwebbeans.properties</code>.</p>
+<p>Read more about our SPIs in <a href="openwebbeans-spi.html">OpenWebBeans
SPI</a></p>
+<h2 id="other-configurable-values">Other Configurable Values<a
class="headerlink" href="#other-configurable-values" title="Permanent
link">¶</a></h2>
+<p>The following configuration values can get tweaked to get tailor OWB to
your specific needs.</p>
+<p>Boolean values can either be <code>true</code>, or <code>TRUE</code>, or
<code>false</code>, or <code>FALSE</code>.</p>
+<table>
+ <tr>
+ <th>Config Key</th>
+ <th>Description</th>
+ <th>Default and sample value</th>
+ </tr>
+ <tr>
+ <td><code>org.apache.webbeans.forceNoCheckedExceptions<code></td>
+ <td>
+ Lifycycle methods like
<code>javax.annotation.PostConstruct</code> and
+ <code>javax.annotation.PreDestroy</code> must not define a
checked Exception
+ regarding to the spec. But this is often unnecessary restrictive
so we
+ allow to disable this check application wide.
+ </td>
+ <td>Defaults to <code>true</code>.</td>
+ </tr>
+ <tr>
+
<td><code>org.apache.webbeans.spi.deployer.useEjbMetaDataDiscoveryService<code></td>
+ <td>Whether to perform EJB discovery or not.</td>
+ <td>Defaults to <code>false</code>. In TomEE this gets automatically
enabled.</td>
+ </tr>
+ <tr>
+ <td><code>org.apache.webbeans.application.jsp<code></td>
+ <td>
+ If enabled, we automatically try to register the ELResolver in the
JSP engine.
+ Enable this setting if you like to access <code>@Named</code> CDI
beans in JSP Expression Language.
+ </td>
+ <td>Default is <code>false</code></td>
+ </tr>
+ <tr>
+ <td><code><code></td>
+ <td></td>
+ <td></td>
+ </tr>
+ <tr>
+ <td><code><code></td>
+ <td></td>
+ <td></td>
+ </tr>
+</table>
+
<h2 id="enable-failover-session-replication-support">Enable FailOver / Session
Replication support<a class="headerlink"
href="#enable-failover-session-replication-support" title="Permanent
link">¶</a></h2>
<h4 id="since-openwebbeans-150">Since OpenWebBeans-1.5.0<a class="headerlink"
href="#since-openwebbeans-150" title="Permanent link">¶</a></h4>
<p>OWB-1.5.x and later does <em>not</em> need any special module or filter to
enable clustering.
