http://git-wip-us.apache.org/repos/asf/incubator-tamaya-site/blob/cddd52a8/documentation-new/extensions/mod_functions.html
----------------------------------------------------------------------
diff --git a/documentation-new/extensions/mod_functions.html 
b/documentation-new/extensions/mod_functions.html
index 8190e93..8f9e358 100644
--- a/documentation-new/extensions/mod_functions.html
+++ b/documentation-new/extensions/mod_functions.html
@@ -125,70 +125,65 @@
                                <h1>Apache Tamaya - Extension: Functions</h1>
                        </div>
 
-                       <p><em>2018-04-26</em></p>
+                       <p><em>2018-05-17</em></p>
 
-                       <p><div id="preamble">
-<div class="sectionbody">
-<!-- toc disabled -->
-</div>
-</div>
-<div class="sect1">
-<h2 id="Functions">Tamaya Functions (Extension Module)</h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>Tamaya <em>Functions</em> is an extension module. Refer to the <a 
href="../extensions.html">extensions documentation</a> for further details.</p>
-</div>
-<div class="sect2">
-<h3 id="_what_functionality_this_module_provides">What functionality this 
module provides ?</h3>
-<div class="paragraph">
-<p>Tamaya <em>Functions</em> provides several functional extensions using the 
UnaryOperator&lt;Config&gt;,Function&lt;Config, T&gt; extension
-points. Most functional extension are accessible from the 
ConfigurationFunctions singleton. Since the JSR API
-does not provide any functional extension points it is recommended to adapt 
the Config instance into .FunctionalConfig.
-Then, when importing the functional methods statically they can very easily 
applied, e.g.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">import static 
org.apache.tamaya.functions.ConfigurationFunctions.*;
+                       <p><div id="preamble"> 
+ <div class="sectionbody"> 
+  <!-- toc disabled --> 
+ </div> 
+</div> 
+<div class="sect1"> 
+ <h2 id="Functions">Tamaya Functions (Extension Module)</h2> 
+ <div class="sectionbody"> 
+  <div class="paragraph"> 
+   <p>Tamaya <em>Functions</em> is an extension module. Refer to the <a 
href="../extensions.html">extensions documentation</a> for further details.</p> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_what_functionality_this_module_provides">What functionality this 
module provides ?</h3> 
+   <div class="paragraph"> 
+    <p>Tamaya <em>Functions</em> provides several functional extensions using 
the UnaryOperator&lt;Config&gt;,Function&lt;Config, T&gt; extension points. 
Most functional extension are accessible from the ConfigurationFunctions 
singleton. Since the JSR API does not provide any functional extension points 
it is recommended to adapt the Config instance into .FunctionalConfig. Then, 
when importing the functional methods statically they can very easily applied, 
e.g.</p> 
+   </div> 
+   <div class="listingblock"> 
+    <div class="content"> 
+     <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">import static 
org.apache.tamaya.functions.ConfigurationFunctions.*;
 
 FunctionalConfig fc = FunctionalConfig.of(ConfigProvider.getConfig());
-Set&lt;String&gt; sections = fc.with(areas("a", 
false).with(transitiveAreas());</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The expression above returns all fully qualified section names that are 
child sections of the root section 'a'.
-So given the entries a.b.entry1, a.b.entry2, a.a.entry3, a.b.c.entry4 the 
reult would be a, a.a, a.b, a.b.c.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_compatibility">Compatibility</h3>
-<div class="paragraph">
-<p>The module is based on Java 8, so it can be used with Java 8 and beyond.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_installation">Installation</h3>
-<div class="paragraph">
-<p>For using the functionality shown in this document you only must add the 
corresponding dependency to your module:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-xml" 
data-lang="xml">&lt;dependency&gt;
+Set&lt;String&gt; sections = fc.with(areas("a", 
false).with(transitiveAreas());</code></pre> 
+    </div> 
+   </div> 
+   <div class="paragraph"> 
+    <p>The expression above returns all fully qualified section names that are 
child sections of the root section 'a'. So given the entries a.b.entry1, 
a.b.entry2, a.a.entry3, a.b.c.entry4 the reult would be a, a.a, a.b, a.b.c.</p> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_compatibility">Compatibility</h3> 
+   <div class="paragraph"> 
+    <p>The module is based on Java 8, so it can be used with Java 8 and 
beyond.</p> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_installation">Installation</h3> 
+   <div class="paragraph"> 
+    <p>For using the functionality shown in this document you only must add 
the corresponding dependency to your module:</p> 
+   </div> 
+   <div class="listingblock"> 
+    <div class="content"> 
+     <pre class="prettyprint highlight"><code class="language-xml" 
data-lang="xml">&lt;dependency&gt;
   &lt;groupId&gt;org.apache.tamaya.ext&lt;/groupId&gt;
   &lt;artifactId&gt;tamaya-functions&lt;/artifactId&gt;
   &lt;version&gt;{tamaya_version}&lt;/version&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_functionalconfig">FunctionalConfig</h3>
-<div class="paragraph">
-<p>The FunctionalConfig actually adds the functional extension points with and 
query to .Config instance, which
-allow to chain expressions as seen in the introductionary snippet:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">public interface FunctionalConfig extends Config, 
ConfigContextSupplier {
+&lt;/dependency&gt;</code></pre> 
+    </div> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_functionalconfig">FunctionalConfig</h3> 
+   <div class="paragraph"> 
+    <p>The FunctionalConfig actually adds the functional extension points with 
and query to .Config instance, which allow to chain expressions as seen in the 
introductionary snippet:</p> 
+   </div> 
+   <div class="listingblock"> 
+    <div class="content"> 
+     <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">public interface FunctionalConfig extends Config, 
ConfigContextSupplier {
 
     /**
      * Enriches a {@link Config} instance with functional access points.
@@ -201,131 +196,57 @@ allow to chain expressions as seen in the 
introductionary snippet:</p>
 
     default FunctionalConfig with(UnaryOperator&lt;Config&gt; operator);
     default &lt;T&gt; T query(Function&lt;Config, T&gt; query);
-}</code></pre>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_the_provided_functions">The Provided Functions</h3>
-<div class="sect3">
-<h4 id="_functions_on_configurationfunctions">Functions on 
ConfigurationFunctions</h4>
-<div class="paragraph">
-<p>The following sections explain the provided functions defined by 
ConfigurationFunctions singleton.</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><strong>UnaryOperator&lt;Config&gt; filter(PropertyMatcher 
matcher)</strong> creates a UnaryOperator&lt;Config&gt; that creates a 
Configuration
-containing only keys that are selected by the given <em>matcher 
predicate</em>. The PropertyMatcher hereby allows to evaluate not only
-the <em>key</em>, but also the <em>value</em>.</p>
-</li>
-<li>
-<p><strong>UnaryOperator&lt;Config&gt; map(KeyMapper keyMapper)</strong> 
creates a UnaryOperator&lt;Config&gt; that maps the keys as defined
-by the given <em>keyMapper</em>.</p>
-</li>
-<li>
-<p><strong>UnaryOperator&lt;Config&gt; section(String section)</strong> 
creates  a UnaryOperator&lt;Config&gt; that creates a Configuration containing 
only
-entries that are direct or indirect members of the given section.</p>
-</li>
-<li>
-<p><strong>UnaryOperator&lt;Config&gt; section(String areaKey, boolean 
stripKeys)</strong> creates  a UnaryOperator&lt;Config&gt; that creates a 
Configuration
-containing only entries that are direct or indirect members of the given 
section. Hereby <em>stripKeys</em> allows to determine
-if the returned entries should be relative to the search criteria 
{{stripKeys=true}} or absolute keys.</p>
-</li>
-<li>
-<p><strong>isKeyInSection(String section, String sectionKey)</strong> allows 
to easily determine if a given <em>key</em> is a direct or indirect member
-of a given section.</p>
-</li>
-<li>
-<p><strong>boolean isKeyInSections(String key, String&#8230;&#8203; 
sectionKeys)</strong> allows to easily determine if one key of given
-<em>key</em> is a direct or indirect member of at least one of the given 
<em>sectionKeys</em>.</p>
-</li>
-<li>
-<p><strong>Function&lt;Config,Set&lt;String&gt;&gt; sections()</strong> allows 
to query all the contained fully qualified section names (the ones that
-also have parameters present).</p>
-</li>
-<li>
-<p><strong>Function&lt;Config,Set&lt;String&gt;&gt; 
transitiveSections()</strong> allows to query all the contained fully qualified 
section names,
-including the transitive closure of sections.</p>
-</li>
-<li>
-<p><strong>Function&lt;Config,Set&lt;String&gt;&gt; sections(final 
Predicate&lt;String&gt; predicate)</strong> allows to query all the contained 
fully
-qualified section names that are selected by the given <em>predicate</em>.</p>
-</li>
-<li>
-<p><strong>Function&lt;Config,Set&lt;String&gt;&gt; sections(final 
Predicate&lt;String&gt; predicate)</strong> allows to query all the contained 
fully
-qualified section names that are selected by the given <em>predicate</em>, 
including the transitive closure of sections
-identified.</p>
-</li>
-<li>
-<p><strong>UnaryOperator&lt;Config&gt; sectionsRecursive(String&#8230;&#8203; 
sectionKeys)</strong> provides a UnaryOperator&lt;Config&gt; that filters all 
sections identified
-by the given <em>sectionKeys</em> and its child sections.</p>
-</li>
-<li>
-<p><strong>UnaryOperator&lt;Config&gt; sectionRecursive(final boolean 
stripKeys, final String&#8230;&#8203; sectionKeys)</strong> provides a 
UnaryOperator&lt;Config&gt;
-that filters all sections identified by the given <em>sectionKeys</em> and its 
child sections. <em>stripKeys</em> allows to
-determine if the resulting configuration should be relative to the selected 
areas ({{stripKeys=true}}) or
-absolute (filtering only).</p>
-</li>
-<li>
-<p><strong>Function&lt;Config,String&gt; jsonInfo()</strong> returns a query 
that converts a Configuration into a JSON formatted String
-representation.</p>
-</li>
-</ul>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_functions_on_configsourcefunctions">Functions on 
ConfigSourceFunctions</h4>
-<div class="paragraph">
-<p>The following sections explain the provided functions defined by 
ConfigSourceFunctions singleton.</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><strong>ConfigSource addMetaData(ConfigSource propertySource, 
Map&lt;String,String&gt; metaData)</strong> Creates a new ConfigSource
-with the given metadata added.</p>
-</li>
-<li>
-<p><strong>boolean isKeyInSection(String key, String sectionKey)</strong> 
Checks if the given <em>key</em> is a direct or indirect member of
-one of the given <em>sectionKey</em>.</p>
-</li>
-<li>
-<p><strong>boolean isKeyInSections(String key, String&#8230;&#8203; 
sectionKeys)</strong> Checks if the given <em>key</em> is a direct or indirect 
member of
-one of one of the given <em>sectionKeys</em>.</p>
-</li>
-<li>
-<p><strong>Set&lt;String&gt; sections(Map&lt;String, String&gt; 
properties)</strong> Extracts the sections from the given properties.</p>
-</li>
-<li>
-<p><strong>Set&lt;String&gt; transitiveSections(Map&lt;String, String&gt; 
properties)</strong> Extracts the transitive sections from the given
-properties.</p>
-</li>
-<li>
-<p><strong>Set&lt;String&gt; sections(Map&lt;String, String&gt; properties, 
final Predicate&lt;String&gt; predicate)</strong> Extracts the sections
-from the given properties, also filtering with the given predicate.</p>
-</li>
-<li>
-<p><strong>Set&lt;String&gt; transitiveSections(Map&lt;String, String&gt; 
properties, Predicate&lt;String&gt; predicate)</strong> Extracts the transitive
-sections from the given properties, also filtering with the given 
predicate.</p>
-</li>
-<li>
-<p><strong>Map&lt;String,String&gt; sectionsRecursive(Map&lt;String, 
String&gt; properties, String&#8230;&#8203; sectionKeys)</strong> Creates w 
ConfigSource
-only containing the sections that a direct or indirect children of the given 
<em>sectionKeys</em>.</p>
-</li>
-<li>
-<p><strong>Map&lt;String,String&gt; sectionRecursive(Map&lt;String, String&gt; 
properties, boolean stripKeys, String&#8230;&#8203; sectionKeys)</strong> 
Creates w ConfigSource
-only containing the sections that a direct or indirect children of the given 
<em>sectionKeys</em>. With <em>stripKeys</em> one can
-select of the returned values should be relative to its selection of be fully 
qualified.</p>
-</li>
-<li>
-<p><strong>String stripSectionKeys(String key, String&#8230;&#8203; 
sectionKeys)</strong> This function strips away the matching section key as 
given
-in <em>sectionKeys</em> from a given <em>key</em>.</p>
-</li>
-</ul>
-</div>
-</div>
-</div>
-</div>
+}</code></pre> 
+    </div> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_the_provided_functions">The Provided Functions</h3> 
+   <div class="sect3"> 
+    <h4 id="_functions_on_configurationfunctions">Functions on 
ConfigurationFunctions</h4> 
+    <div class="paragraph"> 
+     <p>The following sections explain the provided functions defined by 
ConfigurationFunctions singleton.</p> 
+    </div> 
+    <div class="ulist"> 
+     <ul> 
+      <li> <p><strong>UnaryOperator&lt;Config&gt; filter(PropertyMatcher 
matcher)</strong> creates a UnaryOperator&lt;Config&gt; that creates a 
Configuration containing only keys that are selected by the given <em>matcher 
predicate</em>. The PropertyMatcher hereby allows to evaluate not only the 
<em>key</em>, but also the <em>value</em>.</p> </li> 
+      <li> <p><strong>UnaryOperator&lt;Config&gt; map(KeyMapper 
keyMapper)</strong> creates a UnaryOperator&lt;Config&gt; that maps the keys as 
defined by the given <em>keyMapper</em>.</p> </li> 
+      <li> <p><strong>UnaryOperator&lt;Config&gt; section(String 
section)</strong> creates a UnaryOperator&lt;Config&gt; that creates a 
Configuration containing only entries that are direct or indirect members of 
the given section.</p> </li> 
+      <li> <p><strong>UnaryOperator&lt;Config&gt; section(String areaKey, 
boolean stripKeys)</strong> creates a UnaryOperator&lt;Config&gt; that creates 
a Configuration containing only entries that are direct or indirect members of 
the given section. Hereby <em>stripKeys</em> allows to determine if the 
returned entries should be relative to the search criteria {{stripKeys=true}} 
or absolute keys.</p> </li> 
+      <li> <p><strong>isKeyInSection(String section, String 
sectionKey)</strong> allows to easily determine if a given <em>key</em> is a 
direct or indirect member of a given section.</p> </li> 
+      <li> <p><strong>boolean isKeyInSections(String key, String…​ 
sectionKeys)</strong> allows to easily determine if one key of given 
<em>key</em> is a direct or indirect member of at least one of the given 
<em>sectionKeys</em>.</p> </li> 
+      <li> <p><strong>Function&lt;Config,Set&lt;String&gt;&gt; 
sections()</strong> allows to query all the contained fully qualified section 
names (the ones that also have parameters present).</p> </li> 
+      <li> <p><strong>Function&lt;Config,Set&lt;String&gt;&gt; 
transitiveSections()</strong> allows to query all the contained fully qualified 
section names, including the transitive closure of sections.</p> </li> 
+      <li> <p><strong>Function&lt;Config,Set&lt;String&gt;&gt; sections(final 
Predicate&lt;String&gt; predicate)</strong> allows to query all the contained 
fully qualified section names that are selected by the given 
<em>predicate</em>.</p> </li> 
+      <li> <p><strong>Function&lt;Config,Set&lt;String&gt;&gt; sections(final 
Predicate&lt;String&gt; predicate)</strong> allows to query all the contained 
fully qualified section names that are selected by the given 
<em>predicate</em>, including the transitive closure of sections 
identified.</p> </li> 
+      <li> <p><strong>UnaryOperator&lt;Config&gt; 
sectionsRecursive(String…​ sectionKeys)</strong> provides a 
UnaryOperator&lt;Config&gt; that filters all sections identified by the given 
<em>sectionKeys</em> and its child sections.</p> </li> 
+      <li> <p><strong>UnaryOperator&lt;Config&gt; sectionRecursive(final 
boolean stripKeys, final String…​ sectionKeys)</strong> provides a 
UnaryOperator&lt;Config&gt; that filters all sections identified by the given 
<em>sectionKeys</em> and its child sections. <em>stripKeys</em> allows to 
determine if the resulting configuration should be relative to the selected 
areas ({{stripKeys=true}}) or absolute (filtering only).</p> </li> 
+      <li> <p><strong>Function&lt;Config,String&gt; jsonInfo()</strong> 
returns a query that converts a Configuration into a JSON formatted String 
representation.</p> </li> 
+     </ul> 
+    </div> 
+   </div> 
+   <div class="sect3"> 
+    <h4 id="_functions_on_configsourcefunctions">Functions on 
ConfigSourceFunctions</h4> 
+    <div class="paragraph"> 
+     <p>The following sections explain the provided functions defined by 
ConfigSourceFunctions singleton.</p> 
+    </div> 
+    <div class="ulist"> 
+     <ul> 
+      <li> <p><strong>ConfigSource addMetaData(ConfigSource propertySource, 
Map&lt;String,String&gt; metaData)</strong> Creates a new ConfigSource with the 
given metadata added.</p> </li> 
+      <li> <p><strong>boolean isKeyInSection(String key, String 
sectionKey)</strong> Checks if the given <em>key</em> is a direct or indirect 
member of one of the given <em>sectionKey</em>.</p> </li> 
+      <li> <p><strong>boolean isKeyInSections(String key, String…​ 
sectionKeys)</strong> Checks if the given <em>key</em> is a direct or indirect 
member of one of one of the given <em>sectionKeys</em>.</p> </li> 
+      <li> <p><strong>Set&lt;String&gt; sections(Map&lt;String, String&gt; 
properties)</strong> Extracts the sections from the given properties.</p> </li> 
+      <li> <p><strong>Set&lt;String&gt; transitiveSections(Map&lt;String, 
String&gt; properties)</strong> Extracts the transitive sections from the given 
properties.</p> </li> 
+      <li> <p><strong>Set&lt;String&gt; sections(Map&lt;String, String&gt; 
properties, final Predicate&lt;String&gt; predicate)</strong> Extracts the 
sections from the given properties, also filtering with the given 
predicate.</p> </li> 
+      <li> <p><strong>Set&lt;String&gt; transitiveSections(Map&lt;String, 
String&gt; properties, Predicate&lt;String&gt; predicate)</strong> Extracts the 
transitive sections from the given properties, also filtering with the given 
predicate.</p> </li> 
+      <li> <p><strong>Map&lt;String,String&gt; 
sectionsRecursive(Map&lt;String, String&gt; properties, String…​ 
sectionKeys)</strong> Creates w ConfigSource only containing the sections that 
a direct or indirect children of the given <em>sectionKeys</em>.</p> </li> 
+      <li> <p><strong>Map&lt;String,String&gt; sectionRecursive(Map&lt;String, 
String&gt; properties, boolean stripKeys, String…​ sectionKeys)</strong> 
Creates w ConfigSource only containing the sections that a direct or indirect 
children of the given <em>sectionKeys</em>. With <em>stripKeys</em> one can 
select of the returned values should be relative to its selection of be fully 
qualified.</p> </li> 
+      <li> <p><strong>String stripSectionKeys(String key, String…​ 
sectionKeys)</strong> This function strips away the matching section key as 
given in <em>sectionKeys</em> from a given <em>key</em>.</p> </li> 
+     </ul> 
+    </div> 
+   </div> 
+  </div> 
+ </div> 
 </div></p>
 
                        <hr />
@@ -337,8 +258,8 @@ in <em>sectionKeys</em> from a given <em>key</em>.</p>
                    <div id="footer">
                      <div class="container">
                        <p class="muted credit">&copy; 2014-<span>2018</span> 
Apache Software Foundation | Mixed with <a 
href="http://getbootstrap.com/";>Bootstrap v3.1.1</a>
-                                                       | Baked with <a 
href="http://jbake.org";>JBake <span>v2.5.1</span></a>
-                                                       at 
<span>2018-05-03</span> |
+                                                       | Baked with <a 
href="http://jbake.org";>JBake <span>v2.6.1</span></a>
+                                                       at 
<span>2018-05-17</span> |
                                                <a 
class="twitter-follow-button" data-show-count="false" 
href="https://twitter.com/tamayaconf";>Follow @tamayaconf</a><script async 
src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
                                                </p>
                                                <p>

http://git-wip-us.apache.org/repos/asf/incubator-tamaya-site/blob/cddd52a8/documentation-new/extensions/mod_hazelcast.html
----------------------------------------------------------------------
diff --git a/documentation-new/extensions/mod_hazelcast.html 
b/documentation-new/extensions/mod_hazelcast.html
index cef41fc..e70dbbc 100644
--- a/documentation-new/extensions/mod_hazelcast.html
+++ b/documentation-new/extensions/mod_hazelcast.html
@@ -125,81 +125,69 @@
                                <h1>Apache Tamaya - Extension: Integration with 
Hazelcast</h1>
                        </div>
 
-                       <p><em>2018-04-26</em></p>
+                       <p><em>2018-05-17</em></p>
 
-                       <p><div id="preamble">
-<div class="sectionbody">
-<!-- toc disabled -->
-</div>
-</div>
-<div class="sect1">
-<h2 id="Consul">Integration with Hazelcast (Extension Module)</h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>Tamaya <em>Hazelcast</em> is an extension module. Refer to the <a 
href="../extensions.html">extensions documentation</a> for further details.</p>
-</div>
-<div class="sect2">
-<h3 id="_what_functionality_this_module_provides">What functionality this 
module provides ?</h3>
-<div class="paragraph">
-<p>Tamaya <em>Hazelcast</em> provides a property source which uses
-<a href="http://www.hazelcast.org";>Hazelcast</a> as configuration backend. 
Hereby the
-module supports read-only integration (as a HazelcastConfigSource as well
-as a writing configuration changes back (based on Tamaya&#8217;s 
MutableConfiguration API
-defined by the <a href="mod_mutable_config.html">tamaya-mutable-config</a> 
extension module.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_compatibility">Compatibility</h3>
-<div class="paragraph">
-<p>The module is based on Java 8, so it will not run on Java 8 and beyond.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_installation">Installation</h3>
-<div class="paragraph">
-<p>To use <em>tamaya-hazelcast</em> you only must add the corresponding 
dependency to your module:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-xml" 
data-lang="xml">&lt;dependency&gt;
+                       <p><div id="preamble"> 
+ <div class="sectionbody"> 
+  <!-- toc disabled --> 
+ </div> 
+</div> 
+<div class="sect1"> 
+ <h2 id="Consul">Integration with Hazelcast (Extension Module)</h2> 
+ <div class="sectionbody"> 
+  <div class="paragraph"> 
+   <p>Tamaya <em>Hazelcast</em> is an extension module. Refer to the <a 
href="../extensions.html">extensions documentation</a> for further details.</p> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_what_functionality_this_module_provides">What functionality this 
module provides ?</h3> 
+   <div class="paragraph"> 
+    <p>Tamaya <em>Hazelcast</em> provides a property source which uses <a 
href="http://www.hazelcast.org";>Hazelcast</a> as configuration backend. Hereby 
the module supports read-only integration (as a HazelcastConfigSource as well 
as a writing configuration changes back (based on Tamaya’s 
MutableConfiguration API defined by the <a 
href="mod_mutable_config.html">tamaya-mutable-config</a> extension module.</p> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_compatibility">Compatibility</h3> 
+   <div class="paragraph"> 
+    <p>The module is based on Java 8, so it will not run on Java 8 and 
beyond.</p> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_installation">Installation</h3> 
+   <div class="paragraph"> 
+    <p>To use <em>tamaya-hazelcast</em> you only must add the corresponding 
dependency to your module:</p> 
+   </div> 
+   <div class="listingblock"> 
+    <div class="content"> 
+     <pre class="prettyprint highlight"><code class="language-xml" 
data-lang="xml">&lt;dependency&gt;
   &lt;groupId&gt;org.apache.tamaya.ext&lt;/groupId&gt;
   &lt;artifactId&gt;tamaya-hazelcast&lt;/artifactId&gt;
   &lt;version&gt;{tamaya_version}&lt;/version&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_the_extensions_provided">The Extensions Provided</h3>
-<div class="paragraph">
-<p>Hazelcast integration comes basically with 2 artifacts:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>The org.apache.tamaya.hazelcast.HazelcastConfigSource is a ConfigSource. 
The property source is not automatically
-registered. Either register it using the <em>ServiceLoader</em> yourself or 
implement
-and register a corresponding <code>ConfigSourceProvider</code>.</p>
-</li>
-<li>
-<p>If the tamaya-mutable-config module is loaded it is possible to write 
property values back into the consul cluster,
-by accessing a MutableConfiguration using the URI config:hazelcast.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Access of consul key/value pairs is through the normal Tamaya API.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_the_hazelcastconfigsource">The HazelcastConfigSource</h3>
-<div class="paragraph">
-<p>The HazelcastConfigSource is not automatically registered and provides 
different options how to integrate
-Tamaya with Hazelcast.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">/**
+&lt;/dependency&gt;</code></pre> 
+    </div> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_the_extensions_provided">The Extensions Provided</h3> 
+   <div class="paragraph"> 
+    <p>Hazelcast integration comes basically with 2 artifacts:</p> 
+   </div> 
+   <div class="ulist"> 
+    <ul> 
+     <li> <p>The org.apache.tamaya.hazelcast.HazelcastConfigSource is a 
ConfigSource. The property source is not automatically registered. Either 
register it using the <em>ServiceLoader</em> yourself or implement and register 
a corresponding <code>ConfigSourceProvider</code>.</p> </li> 
+     <li> <p>If the tamaya-mutable-config module is loaded it is possible to 
write property values back into the consul cluster, by accessing a 
MutableConfiguration using the URI config:hazelcast.</p> </li> 
+    </ul> 
+   </div> 
+   <div class="paragraph"> 
+    <p>Access of consul key/value pairs is through the normal Tamaya API.</p> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_the_hazelcastconfigsource">The HazelcastConfigSource</h3> 
+   <div class="paragraph"> 
+    <p>The HazelcastConfigSource is not automatically registered and provides 
different options how to integrate Tamaya with Hazelcast.</p> 
+   </div> 
+   <div class="listingblock"> 
+    <div class="content"> 
+     <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">/**
  * Creates a new instance, hereby using {@code "Hazelcast"} as property source 
name and
  * a default hazelcast backend created by calling {@link 
Hazelcast#newHazelcastInstance()}.
  */
@@ -233,17 +221,15 @@ public HazelcastConfigSource(String name, Config config);
  * @param name
  * @param hazelcastInstance
  */
-public HazelcastConfigSource(String name, HazelcastInstance 
hazelcastInstance);</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>To use hazelcast as a configuration backend, you simply create the 
corresponding Hazelcast instance
-and use it to initialize the Tamaya property source. Given that a hazelcast 
backedn configuration
-can be easily created asillustrated below:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">// define config settings
+public HazelcastConfigSource(String name, HazelcastInstance 
hazelcastInstance);</code></pre> 
+    </div> 
+   </div> 
+   <div class="paragraph"> 
+    <p>To use hazelcast as a configuration backend, you simply create the 
corresponding Hazelcast instance and use it to initialize the Tamaya property 
source. Given that a hazelcast backedn configuration can be easily created 
asillustrated below:</p> 
+   </div> 
+   <div class="listingblock"> 
+    <div class="content"> 
+     <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">// define config settings
 HazelcastInstance hazelcastInstance = Hazelcast.newInstance(hazelcastConfig);
 HazelcastConfigSource cs = new HazelcastConfigSource(hazelcastInstance);
 cs.setName("myHazelcast-config");
@@ -254,11 +240,11 @@ 
b.addDiscoveredConverters().addDefaultSources().addDiscoveredSources();
 // Add the hazelcast property source (as most significant)
 b.awithSource(cs);
 // build and use the configuration
-Config config = b.build();</code></pre>
-</div>
-</div>
-</div>
-</div>
+Config config = b.build();</code></pre> 
+    </div> 
+   </div> 
+  </div> 
+ </div> 
 </div></p>
 
                        <hr />
@@ -270,8 +256,8 @@ Config config = b.build();</code></pre>
                    <div id="footer">
                      <div class="container">
                        <p class="muted credit">&copy; 2014-<span>2018</span> 
Apache Software Foundation | Mixed with <a 
href="http://getbootstrap.com/";>Bootstrap v3.1.1</a>
-                                                       | Baked with <a 
href="http://jbake.org";>JBake <span>v2.5.1</span></a>
-                                                       at 
<span>2018-05-03</span> |
+                                                       | Baked with <a 
href="http://jbake.org";>JBake <span>v2.6.1</span></a>
+                                                       at 
<span>2018-05-17</span> |
                                                <a 
class="twitter-follow-button" data-show-count="false" 
href="https://twitter.com/tamayaconf";>Follow @tamayaconf</a><script async 
src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
                                                </p>
                                                <p>

http://git-wip-us.apache.org/repos/asf/incubator-tamaya-site/blob/cddd52a8/documentation-new/extensions/mod_injection.html
----------------------------------------------------------------------
diff --git a/documentation-new/extensions/mod_injection.html 
b/documentation-new/extensions/mod_injection.html
index a7409c7..87c6d04 100644
--- a/documentation-new/extensions/mod_injection.html
+++ b/documentation-new/extensions/mod_injection.html
@@ -125,91 +125,81 @@
                                <h1>Apache Tamaya - Extension: Injection</h1>
                        </div>
 
-                       <p><em>2018-05-02</em></p>
-
-                       <p><div id="preamble">
-<div class="sectionbody">
-<!-- toc disabled -->
-</div>
-</div>
-<div class="sect1">
-<h2 id="Injection">Tamaya Injection (Extension Module)</h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>Tamaya <em>Injection</em> is an extension module. Refer to the <a 
href="../extensions.html">extensions documentation</a> for further details.</p>
-</div>
-<div class="sect2">
-<h3 id="_what_functionality_this_module_provides">What functionality this 
module provides ?</h3>
-<div class="paragraph">
-<p>Tamaya <em>Injection</em> provides functionality for injecting configured 
values into beans, or creating configuration
-template instances.</p>
-</div>
-<div class="paragraph">
-<p>Inversion of Control (aka IoC/Hollywood Principle) has proven to be very 
useful and effective in avoiding boilerplate
-code. In Java there are different frameworks available that all provide IoC 
mechanisms. Unfortunately IoC is not a
-built-in language feature. So for a portable solution that works also in Java 
SE Tamaya itself has to provide the
-according injection services. This module adds this functionality to 
Tamaya.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_compatibility">Compatibility</h3>
-<div class="paragraph">
-<p>The module is based on Java 8, so it can be used with Java 8 and beyond.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_installation">Installation</h3>
-<div class="paragraph">
-<p>The basic injection API is defined by the configuration JSRßs API. 
Nevertheless Tamaya&#8217;s adds some
-useful extensions. These extensions are deployed as optional API artifact:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-xml" 
data-lang="xml">&lt;dependency&gt;
+                       <p><em>2018-05-17</em></p>
+
+                       <p><div id="preamble"> 
+ <div class="sectionbody"> 
+  <!-- toc disabled --> 
+ </div> 
+</div> 
+<div class="sect1"> 
+ <h2 id="Injection">Tamaya Injection (Extension Module)</h2> 
+ <div class="sectionbody"> 
+  <div class="paragraph"> 
+   <p>Tamaya <em>Injection</em> is an extension module. Refer to the <a 
href="../extensions.html">extensions documentation</a> for further details.</p> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_what_functionality_this_module_provides">What functionality this 
module provides ?</h3> 
+   <div class="paragraph"> 
+    <p>Tamaya <em>Injection</em> provides functionality for injecting 
configured values into beans, or creating configuration template instances.</p> 
+   </div> 
+   <div class="paragraph"> 
+    <p>Inversion of Control (aka IoC/Hollywood Principle) has proven to be 
very useful and effective in avoiding boilerplate code. In Java there are 
different frameworks available that all provide IoC mechanisms. Unfortunately 
IoC is not a built-in language feature. So for a portable solution that works 
also in Java SE Tamaya itself has to provide the according injection services. 
This module adds this functionality to Tamaya.</p> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_compatibility">Compatibility</h3> 
+   <div class="paragraph"> 
+    <p>The module is based on Java 8, so it can be used with Java 8 and 
beyond.</p> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_installation">Installation</h3> 
+   <div class="paragraph"> 
+    <p>The basic injection API is defined by the configuration JSRßs API. 
Nevertheless Tamaya’s adds some useful extensions. These extensions are 
deployed as optional API artifact:</p> 
+   </div> 
+   <div class="listingblock"> 
+    <div class="content"> 
+     <pre class="prettyprint highlight"><code class="language-xml" 
data-lang="xml">&lt;dependency&gt;
   &lt;groupId&gt;org.apache.tamaya.ext&lt;/groupId&gt;
   &lt;artifactId&gt;tamaya-injection-api&lt;/artifactId&gt;
   &lt;version&gt;{tamaya_version}&lt;/version&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>To use injection with Java SE you must add the corresponding dependency to 
your module:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-xml" 
data-lang="xml">&lt;dependency&gt;
+&lt;/dependency&gt;</code></pre> 
+    </div> 
+   </div> 
+   <div class="paragraph"> 
+    <p>To use injection with Java SE you must add the corresponding dependency 
to your module:</p> 
+   </div> 
+   <div class="listingblock"> 
+    <div class="content"> 
+     <pre class="prettyprint highlight"><code class="language-xml" 
data-lang="xml">&lt;dependency&gt;
   &lt;groupId&gt;org.apache.tamaya.ext&lt;/groupId&gt;
   &lt;artifactId&gt;tamaya-injection&lt;/artifactId&gt;
   &lt;version&gt;{tamaya_version}&lt;/version&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Similarly there are other injection implementations available, targetig 
platforms such as</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><a href="mod_spring.html">Spring, Spring Boot</a></p>
-</li>
-<li>
-<p><a href="mod_CDI.html">Java EE/CDI</a></p>
-</li>
-</ul>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_core_concepts">Core Concepts</h3>
-<div class="paragraph">
-<p>Basically you annotate fields or methods in your beans with @ConfigProperty 
to enable configuration injection. Tamaya
-additionally defines further annotations that allo you to define additional 
aspects such as default values, custom
-converters etc. The following example illustrates the basic functionality:
-code snippet:</p>
-</div>
-<div class="listingblock">
-<div class="title">Annotated Example Class</div>
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">package foo.bar;
+&lt;/dependency&gt;</code></pre> 
+    </div> 
+   </div> 
+   <div class="paragraph"> 
+    <p>Similarly there are other injection implementations available, targetig 
platforms such as</p> 
+   </div> 
+   <div class="ulist"> 
+    <ul> 
+     <li> <p><a href="mod_spring.html">Spring, Spring Boot</a></p> </li> 
+     <li> <p><a href="mod_CDI.html">Java EE/CDI</a></p> </li> 
+    </ul> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_core_concepts">Core Concepts</h3> 
+   <div class="paragraph"> 
+    <p>Basically you annotate fields or methods in your beans with 
@ConfigProperty to enable configuration injection. Tamaya additionally defines 
further annotations that allo you to define additional aspects such as default 
values, custom converters etc. The following example illustrates the basic 
functionality: code snippet:</p> 
+   </div> 
+   <div class="listingblock"> 
+    <div class="title">
+     Annotated Example Class
+    </div> 
+    <div class="content"> 
+     <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">package foo.bar;
 
 public class ConfiguredClass {
 
@@ -240,17 +230,18 @@ public class ConfiguredClass {
     private BigDecimal bigNumber;
 
     ...
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>When configuring data or configuration classes it is also possible to 
auto-inject the fields identified. For activating
-this feature a class must be annotated with @ConfigAutoDetect:</p>
-</div>
-<div class="listingblock">
-<div class="title">An autoinjected bean class</div>
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">package a.b;
+}</code></pre> 
+    </div> 
+   </div> 
+   <div class="paragraph"> 
+    <p>When configuring data or configuration classes it is also possible to 
auto-inject the fields identified. For activating this feature a class must be 
annotated with @ConfigAutoDetect:</p> 
+   </div> 
+   <div class="listingblock"> 
+    <div class="title">
+     An autoinjected bean class
+    </div> 
+    <div class="content"> 
+     <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">package a.b;
 
 @ConfigAutoDetect
 public final class Tenant {
@@ -269,218 +260,198 @@ public final class Tenant {
   public String getDescription(){
     return description;
   }
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>These examples do not show all possibilities provided. Configuring instance 
of these
-class using Tamaya is very simple: Just pass the instance to Tamaya to let
-Tamaya inject the configuration:</p>
-</div>
-<div class="listingblock">
-<div class="title">Configuring the ConfiguredClass Instance</div>
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">ConfiguredClass classInstance = new ConfiguredClass();
+}</code></pre> 
+    </div> 
+   </div> 
+   <div class="paragraph"> 
+    <p>These examples do not show all possibilities provided. Configuring 
instance of these class using Tamaya is very simple: Just pass the instance to 
Tamaya to let Tamaya inject the configuration:</p> 
+   </div> 
+   <div class="listingblock"> 
+    <div class="title">
+     Configuring the ConfiguredClass Instance
+    </div> 
+    <div class="content"> 
+     <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">ConfiguredClass classInstance = new ConfiguredClass();
 ConfigurationInjector.configure(configuredClass);
 
 Tenant tenant = new Tenant();
-ConfigurationInjector.configure(tenant);</code></pre>
-</div>
-</div>
-<div class="admonitionblock note">
-<table>
-<tr>
-<td class="icon">
-<div class="title">Note</div>
-</td>
-<td class="content">
-Configuration injection works similarly, when used with other integration 
modules, e.g. when Tamaya is used
-with CDI, Spring or within an OSGI container. For further details refer also 
to the corresponding integration module&#8217;s
-documentation.
-</td>
-</tr>
-</table>
-</div>
-<div class="sect3">
-<h4 id="_the_configurationinjector">The ConfigurationInjector</h4>
-<div class="paragraph">
-<p>The ConfigurationInjector interface provides methods that allow any kind of 
instances to be configured
-by passing the instances to T 
ConfigurationInjector.getInstance().configure(T);. The classes passed
-hereby must not be annotated with @ConfigProperty for being configurable.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_accessing_supplier_instances">Accessing Supplier instances</h4>
-<div class="paragraph">
-<p>In many cases you want to create a supplier that simply creates instances 
that are correctly configured as defined
-by the current context. This can be done using Suppliers:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">Supplier&lt;Tenant&gt; configuredTenantSupplier = 
ConfigurationInjector.getInstance().getConfiguredSupplier(
+ConfigurationInjector.configure(tenant);</code></pre> 
+    </div> 
+   </div> 
+   <div class="admonitionblock note"> 
+    <table> 
+     <tbody>
+      <tr> 
+       <td class="icon"> 
+        <div class="title">
+         Note
+        </div> </td> 
+       <td class="content"> Configuration injection works similarly, when used 
with other integration modules, e.g. when Tamaya is used with CDI, Spring or 
within an OSGI container. For further details refer also to the corresponding 
integration module’s documentation. </td> 
+      </tr> 
+     </tbody>
+    </table> 
+   </div> 
+   <div class="sect3"> 
+    <h4 id="_the_configurationinjector">The ConfigurationInjector</h4> 
+    <div class="paragraph"> 
+     <p>The ConfigurationInjector interface provides methods that allow any 
kind of instances to be configured by passing the instances to T 
ConfigurationInjector.getInstance().configure(T);. The classes passed hereby 
must not be annotated with @ConfigProperty for being configurable.</p> 
+    </div> 
+   </div> 
+   <div class="sect3"> 
+    <h4 id="_accessing_supplier_instances">Accessing Supplier instances</h4> 
+    <div class="paragraph"> 
+     <p>In many cases you want to create a supplier that simply creates 
instances that are correctly configured as defined by the current context. This 
can be done using Suppliers:</p> 
+    </div> 
+    <div class="listingblock"> 
+     <div class="content"> 
+      <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">Supplier&lt;Tenant&gt; configuredTenantSupplier = 
ConfigurationInjector.getInstance().getConfiguredSupplier(
   new Supplier&lt;Tenant&gt;(){
      public Tenant get(){
        return new Tenant();
      }
-});</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>With Java 8 it&#8217;s even more simple:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">Supplier&lt;Tenant&gt; configuredTenantSupplier = 
ConfigurationInjector.getInstance().getConfiguredSupplier(
-  Tenant::new);</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Hereby this annotation can be used in multiple ways and combined with other 
annotations such as
-@WithLoadPolicy, @WithConverter.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_minimal_example">Minimal Example</h4>
-<div class="paragraph">
-<p>To illustrate the mechanism below the most simple variant of a configured 
class is given:</p>
-</div>
-<div class="listingblock">
-<div class="title">Most simple configured class</div>
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">pubic class ConfiguredItem{
+});</code></pre> 
+     </div> 
+    </div> 
+    <div class="paragraph"> 
+     <p>With Java 8 it’s even more simple:</p> 
+    </div> 
+    <div class="listingblock"> 
+     <div class="content"> 
+      <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">Supplier&lt;Tenant&gt; configuredTenantSupplier = 
ConfigurationInjector.getInstance().getConfiguredSupplier(
+  Tenant::new);</code></pre> 
+     </div> 
+    </div> 
+    <div class="paragraph"> 
+     <p>Hereby this annotation can be used in multiple ways and combined with 
other annotations such as @WithLoadPolicy, @WithConverter.</p> 
+    </div> 
+   </div> 
+   <div class="sect3"> 
+    <h4 id="_minimal_example">Minimal Example</h4> 
+    <div class="paragraph"> 
+     <p>To illustrate the mechanism below the most simple variant of a 
configured class is given:</p> 
+    </div> 
+    <div class="listingblock"> 
+     <div class="title">
+      Most simple configured class
+     </div> 
+     <div class="content"> 
+      <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">pubic class ConfiguredItem{
   @Config
   private String aValue;
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>When this class is configured, e.g. by passing it to 
ConfigurationInjector.getInstance().configure(Object),
-the following is happening:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>The current valid Config is evaluated by calling Config cfg = 
ConfigProvider.getConfig();</p>
-</li>
-<li>
-<p>The current property value (String) is evaluated by calling 
cfg.getValue("aValue", Type.class);
-for each possible key (mutliple keys are possible).</p>
-</li>
-<li>
-<p>if not successful, an error is thrown</p>
-</li>
-<li>
-<p>On success, since no type conversion is involved, the value is injected.</p>
-</li>
-</ul>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_the_annotations_in_detail">The Annotations in detail</h3>
-<div class="sect3">
-<h4 id="_using_code_configproperty_code">Using 
<code>@ConfigProperty</code></h4>
-<div class="paragraph">
-<p>This is the main JSR annotation targeting a field in a class for 
configuration injection.</p>
-</div>
-<div class="sect4">
-<h5 id="_evaluating_of_em_configuration_keys_em">Evaluating of 
<em>configuration keys</em></h5>
-<div class="paragraph">
-<p>By default Tamaya tries to determine configuration for each property of an 
instance
-passed, using the following resolution policy:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Given a class a.b.MyClass and a field myField it would try to look up the
-following keys:</p>
-</li>
-</ul>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-listing" 
data-lang="listing">a.b.MyClass.myField
+}</code></pre> 
+     </div> 
+    </div> 
+    <div class="paragraph"> 
+     <p>When this class is configured, e.g. by passing it to 
ConfigurationInjector.getInstance().configure(Object), the following is 
happening:</p> 
+    </div> 
+    <div class="ulist"> 
+     <ul> 
+      <li> <p>The current valid Config is evaluated by calling Config cfg = 
ConfigProvider.getConfig();</p> </li> 
+      <li> <p>The current property value (String) is evaluated by calling 
cfg.getValue("aValue", Type.class); for each possible key (mutliple keys are 
possible).</p> </li> 
+      <li> <p>if not successful, an error is thrown</p> </li> 
+      <li> <p>On success, since no type conversion is involved, the value is 
injected.</p> </li> 
+     </ul> 
+    </div> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_the_annotations_in_detail">The Annotations in detail</h3> 
+   <div class="sect3"> 
+    <h4 id="_using_code_configproperty_code">Using 
<code>@ConfigProperty</code></h4> 
+    <div class="paragraph"> 
+     <p>This is the main JSR annotation targeting a field in a class for 
configuration injection.</p> 
+    </div> 
+    <div class="sect4"> 
+     <h5 id="_evaluating_of_em_configuration_keys_em">Evaluating of 
<em>configuration keys</em></h5> 
+     <div class="paragraph"> 
+      <p>By default Tamaya tries to determine configuration for each property 
of an instance passed, using the following resolution policy:</p> 
+     </div> 
+     <div class="ulist"> 
+      <ul> 
+       <li> <p>Given a class a.b.MyClass and a field myField it would try to 
look up the following keys:</p> </li> 
+      </ul> 
+     </div> 
+     <div class="listingblock"> 
+      <div class="content"> 
+       <pre class="prettyprint highlight"><code class="language-listing" 
data-lang="listing">a.b.MyClass.myField
 a.b.MyClass.my-field
 MyClass.myField
 MyClass.my-field
 myField
-my-field</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>This behaviour can be adapted, e.g. by using the 
<code>@ConfigDefaultSections</code> annotation on the
-declaring type:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre>@ConfigDefaultSections("a.b.c", "deprecated")
+my-field</code></pre> 
+      </div> 
+     </div> 
+     <div class="paragraph"> 
+      <p>This behaviour can be adapted, e.g. by using the 
<code>@ConfigDefaultSections</code> annotation on the declaring type:</p> 
+     </div> 
+     <div class="listingblock"> 
+      <div class="content"> 
+       <pre>@ConfigDefaultSections("a.b.c", "deprecated")
 pubic class MyClass{
   @ConfigProperty
   private String myField;
-}</pre>
-</div>
-</div>
-<div class="paragraph">
-<p>This will result in a modified lookup chain as illustrated below:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-listing" 
data-lang="listing">a.b.c.myField
+}</pre> 
+      </div> 
+     </div> 
+     <div class="paragraph"> 
+      <p>This will result in a modified lookup chain as illustrated below:</p> 
+     </div> 
+     <div class="listingblock"> 
+      <div class="content"> 
+       <pre class="prettyprint highlight"><code class="language-listing" 
data-lang="listing">a.b.c.myField
 a.b.c.my-field
 deprecated.myField
-deprecated.my-field</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>This helps to reduce redundancy when referring to you configuration keys. 
Additionally
-it is also possible to define absolute key entries, e.g.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre>@ConfigDefaultSections("a.b.c")
+deprecated.my-field</code></pre> 
+      </div> 
+     </div> 
+     <div class="paragraph"> 
+      <p>This helps to reduce redundancy when referring to you configuration 
keys. Additionally it is also possible to define absolute key entries, e.g.</p> 
+     </div> 
+     <div class="listingblock"> 
+      <div class="content"> 
+       <pre>@ConfigDefaultSections("a.b.c")
 pubic class MyClass{
   @ConfigProperty("myField" /* relative */)
   @ConfigFallbackKeys("[absolute.key]")
   private String myField;
-}</pre>
-</div>
-</div>
-<div class="paragraph">
-<p>This will result in a lookup chain as illustrated below:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-listing" 
data-lang="listing">a.b.c.myField
-absolute.key # default sections are ignored</code></pre>
-</div>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_using_defaults">Using defaults</h5>
-<div class="paragraph">
-<p>In the next example we explicitly define the <em>default</em> property 
value:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">pubic class ConfiguredItem{
+}</pre> 
+      </div> 
+     </div> 
+     <div class="paragraph"> 
+      <p>This will result in a lookup chain as illustrated below:</p> 
+     </div> 
+     <div class="listingblock"> 
+      <div class="content"> 
+       <pre class="prettyprint highlight"><code class="language-listing" 
data-lang="listing">a.b.c.myField
+absolute.key # default sections are ignored</code></pre> 
+      </div> 
+     </div> 
+    </div> 
+    <div class="sect4"> 
+     <h5 id="_using_defaults">Using defaults</h5> 
+     <div class="paragraph"> 
+      <p>In the next example we explicitly define the <em>default</em> 
property value:</p> 
+     </div> 
+     <div class="listingblock"> 
+      <div class="content"> 
+       <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">pubic class ConfiguredItem{
 
   @ConfigProperty(key="aValue", defaultValue="${env:java.version}")
   @ConfigFallbackKeys({"a.b.value","a.b.deprecated.value"})
   private String aValue;
-}</code></pre>
-</div>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 
id="_automatically_inject_all_items_using_code_configautoinject_code">Automatically
 inject all items using <code>@ConfigAutoInject</code></h4>
-<div class="paragraph">
-<p>Using <code>@ConfigAutoDetect</code> allows you to automatically select all 
properties found for
-configuration injection:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">@ConfigAutoDetect
+}</code></pre> 
+      </div> 
+     </div> 
+    </div> 
+   </div> 
+   <div class="sect3"> 
+    <h4 
id="_automatically_inject_all_items_using_code_configautoinject_code">Automatically
 inject all items using <code>@ConfigAutoInject</code></h4> 
+    <div class="paragraph"> 
+     <p>Using <code>@ConfigAutoDetect</code> allows you to automatically 
select all properties found for configuration injection:</p> 
+    </div> 
+    <div class="listingblock"> 
+     <div class="content"> 
+      <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">@ConfigAutoDetect
 pubic class ConfiguredItem{
 
   private transient int sum;
@@ -488,65 +459,59 @@ pubic class ConfiguredItem{
   private String a;
   private String b;
   Private String c;
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Adding the <code>@NoConfig</code> annotation prevents a field or method to 
be auto-detected from
-configuration. This is especially useful, if a type is annotated as 
@ConfigAutoDetect with auto-confiuration
-turned on as follows:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">@NoConfig
-private transient int sum;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>In this case the fields a,b,c are configured, whereas the field sum is 
ignored regarding
-configuration.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 
id="_adding_custom_property_converters_using_code_withconverter_code">Adding 
custom property converters using <code>@WithConverter</code></h4>
-<div class="paragraph">
-<p>The @WithConverter annotation allows you to define a class of type 
Converter, to be applied
-on a property configured to convert the String value to the expected injected 
type. This can be used for
-various use cases, e.g. adding custom formats, config models, decryption.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">pubic class ConfiguredItem{
+}</code></pre> 
+     </div> 
+    </div> 
+    <div class="paragraph"> 
+     <p>Adding the <code>@NoConfig</code> annotation prevents a field or 
method to be auto-detected from configuration. This is especially useful, if a 
type is annotated as @ConfigAutoDetect with auto-confiuration turned on as 
follows:</p> 
+    </div> 
+    <div class="listingblock"> 
+     <div class="content"> 
+      <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">@NoConfig
+private transient int sum;</code></pre> 
+     </div> 
+    </div> 
+    <div class="paragraph"> 
+     <p>In this case the fields a,b,c are configured, whereas the field sum is 
ignored regarding configuration.</p> 
+    </div> 
+   </div> 
+   <div class="sect3"> 
+    <h4 
id="_adding_custom_property_converters_using_code_withconverter_code">Adding 
custom property converters using <code>@WithConverter</code></h4> 
+    <div class="paragraph"> 
+     <p>The @WithConverter annotation allows you to define a class of type 
Converter, to be applied on a property configured to convert the String value 
to the expected injected type. This can be used for various use cases, e.g. 
adding custom formats, config models, decryption.</p> 
+    </div> 
+    <div class="listingblock"> 
+     <div class="content"> 
+      <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">pubic class ConfiguredItem{
 
   @WithConverter(MyPropertyConverter.class)
   @ConfigProperty
   private String a;
 
-}</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_inject_a_code_dynamicvalue_code">Inject a 
<code>DynamicValue</code></h4>
-<div class="paragraph">
-<p>Within this example we evaluate a dynamic value. This mechanism allows you 
to listen for configuration changes and to
-commit new values exactly, when convenient for you.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">pubic class ConfiguredItem{
+}</code></pre> 
+     </div> 
+    </div> 
+   </div> 
+   <div class="sect3"> 
+    <h4 id="_inject_a_code_dynamicvalue_code">Inject a 
<code>DynamicValue</code></h4> 
+    <div class="paragraph"> 
+     <p>Within this example we evaluate a dynamic value. This mechanism allows 
you to listen for configuration changes and to commit new values exactly, when 
convenient for you.</p> 
+    </div> 
+    <div class="listingblock"> 
+     <div class="content"> 
+      <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">pubic class ConfiguredItem{
 
   @ConfigProperty(key="aValue", defaultValue="${env:java.version}")
   private DynamicValue aValue;
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The DynamicValue provides you the following functionality:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">public interface DynamicValue&lt;T&gt; {
+}</code></pre> 
+     </div> 
+    </div> 
+    <div class="paragraph"> 
+     <p>The DynamicValue provides you the following functionality:</p> 
+    </div> 
+    <div class="listingblock"> 
+     <div class="content"> 
+      <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">public interface DynamicValue&lt;T&gt; {
 
     T get();
     T getNewValue();
@@ -574,38 +539,30 @@ public enum UpdatePolicy{
     EXPLCIT,
     NEVER,
     LOG_AND_DISCARD
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Summarizing a DynamicValue allows you</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>to reload actively updates of configured values.</p>
-</li>
-<li>
-<p>update implicitly or explicitly all changes on the value.</p>
-</li>
-<li>
-<p>add listeners that observe changes of a certain value.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Dynamic values also allow on-the-fly reevaluation of the value by calling 
evaluateValue(). Hereby the value of the
-instance is not changed.</p>
-</div>
-<div class="sect4">
-<h5 id="_the_loadpolicy_enum">The LoadPolicy enum</h5>
-<div class="paragraph">
-<p>The LoadPolicy enum defines different configuration loading behaviour
-to be applied:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">@Deprecated
+}</code></pre> 
+     </div> 
+    </div> 
+    <div class="paragraph"> 
+     <p>Summarizing a DynamicValue allows you</p> 
+    </div> 
+    <div class="ulist"> 
+     <ul> 
+      <li> <p>to reload actively updates of configured values.</p> </li> 
+      <li> <p>update implicitly or explicitly all changes on the value.</p> 
</li> 
+      <li> <p>add listeners that observe changes of a certain value.</p> </li> 
+     </ul> 
+    </div> 
+    <div class="paragraph"> 
+     <p>Dynamic values also allow on-the-fly reevaluation of the value by 
calling evaluateValue(). Hereby the value of the instance is not changed.</p> 
+    </div> 
+    <div class="sect4"> 
+     <h5 id="_the_loadpolicy_enum">The LoadPolicy enum</h5> 
+     <div class="paragraph"> 
+      <p>The LoadPolicy enum defines different configuration loading behaviour 
to be applied:</p> 
+     </div> 
+     <div class="listingblock"> 
+      <div class="content"> 
+       <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">@Deprecated
 public enum LoadPolicy {
     /**
      * The configuration keys is evaluated once, when the owning component is 
loaded/configured, but never updated later.
@@ -621,41 +578,33 @@ public enum LoadPolicy {
      * The configuration value is evaluated every time it is accessed.
      */
     ALWAYS
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>This enum type currently is used only internally, so avoid using it as of
-now in your code is recommended.</p>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_configuration_events">Configuration Events</h3>
-<div class="paragraph">
-<p>Similar to CDI Tamaya publishes Configuration events, when instances were 
configured. It depends on the effective
-event backend in use, if and how events are published:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>when you have the CDI extension active events are published using the 
default CDI event mechanism.</p>
-</li>
-<li>
-<p>in all other scenarios events are delegated to the tamaya-events module, if 
available,</p>
-</li>
-<li>
-<p>if no event delegation is available no events are published.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>The event published is very simple:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">public interface ConfiguredType {
+}</code></pre> 
+      </div> 
+     </div> 
+     <div class="paragraph"> 
+      <p>This enum type currently is used only internally, so avoid using it 
as of now in your code is recommended.</p> 
+     </div> 
+    </div> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_configuration_events">Configuration Events</h3> 
+   <div class="paragraph"> 
+    <p>Similar to CDI Tamaya publishes Configuration events, when instances 
were configured. It depends on the effective event backend in use, if and how 
events are published:</p> 
+   </div> 
+   <div class="ulist"> 
+    <ul> 
+     <li> <p>when you have the CDI extension active events are published using 
the default CDI event mechanism.</p> </li> 
+     <li> <p>in all other scenarios events are delegated to the tamaya-events 
module, if available,</p> </li> 
+     <li> <p>if no event delegation is available no events are published.</p> 
</li> 
+    </ul> 
+   </div> 
+   <div class="paragraph"> 
+    <p>The event published is very simple:</p> 
+   </div> 
+   <div class="listingblock"> 
+    <div class="content"> 
+     <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">public interface ConfiguredType {
     Class getType();
     String getName();
     Collection&lt;ConfiguredField&gt; getConfiguredFields();
@@ -680,11 +629,11 @@ public interface ConfiguredMethod {
     String getSignature();
     void configure(Object instance, Configuration config);
 }
-----------------------------------------</code></pre>
-</div>
-</div>
-</div>
-</div>
+----------------------------------------</code></pre> 
+    </div> 
+   </div> 
+  </div> 
+ </div> 
 </div></p>
 
                        <hr />
@@ -696,8 +645,8 @@ public interface ConfiguredMethod {
                    <div id="footer">
                      <div class="container">
                        <p class="muted credit">&copy; 2014-<span>2018</span> 
Apache Software Foundation | Mixed with <a 
href="http://getbootstrap.com/";>Bootstrap v3.1.1</a>
-                                                       | Baked with <a 
href="http://jbake.org";>JBake <span>v2.5.1</span></a>
-                                                       at 
<span>2018-05-03</span> |
+                                                       | Baked with <a 
href="http://jbake.org";>JBake <span>v2.6.1</span></a>
+                                                       at 
<span>2018-05-17</span> |
                                                <a 
class="twitter-follow-button" data-show-count="false" 
href="https://twitter.com/tamayaconf";>Follow @tamayaconf</a><script async 
src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
                                                </p>
                                                <p>

http://git-wip-us.apache.org/repos/asf/incubator-tamaya-site/blob/cddd52a8/documentation-new/extensions/mod_jndi.html
----------------------------------------------------------------------
diff --git a/documentation-new/extensions/mod_jndi.html 
b/documentation-new/extensions/mod_jndi.html
index 1382a93..eb6f0ec 100644
--- a/documentation-new/extensions/mod_jndi.html
+++ b/documentation-new/extensions/mod_jndi.html
@@ -125,57 +125,54 @@
                                <h1>Apache Tamaya - Extension: Integration with 
JNDI</h1>
                        </div>
 
-                       <p><em>2018-04-26</em></p>
+                       <p><em>2018-05-17</em></p>
 
-                       <p><div id="preamble">
-<div class="sectionbody">
-<!-- toc disabled -->
-</div>
-</div>
-<div class="sect1">
-<h2 id="JNDI">Integration with JNDI (Extension Module)</h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>Tamaya <em>JNDI</em> is an extension module. Refer to the <a 
href="../extensions.html">extensions documentation</a> for further details.</p>
-</div>
-<div class="sect2">
-<h3 id="_what_functionality_this_module_provides">What functionality this 
module provides ?</h3>
-<div class="paragraph">
-<p>Tamaya <em>JNDI</em> provides a simple ConfigySource that reads values from 
a
-JNDI context.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_compatibility">Compatibility</h3>
-<div class="paragraph">
-<p>The module is based on Java 8, so it will not run on Java 8 and beyond.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_installation">Installation</h3>
-<div class="paragraph">
-<p>To use <em>jndi</em> as a configuration backend you only must add the 
corresponding dependency to
-your module:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-xml" 
data-lang="xml">&lt;dependency&gt;
+                       <p><div id="preamble"> 
+ <div class="sectionbody"> 
+  <!-- toc disabled --> 
+ </div> 
+</div> 
+<div class="sect1"> 
+ <h2 id="JNDI">Integration with JNDI (Extension Module)</h2> 
+ <div class="sectionbody"> 
+  <div class="paragraph"> 
+   <p>Tamaya <em>JNDI</em> is an extension module. Refer to the <a 
href="../extensions.html">extensions documentation</a> for further details.</p> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_what_functionality_this_module_provides">What functionality this 
module provides ?</h3> 
+   <div class="paragraph"> 
+    <p>Tamaya <em>JNDI</em> provides a simple ConfigySource that reads values 
from a JNDI context.</p> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_compatibility">Compatibility</h3> 
+   <div class="paragraph"> 
+    <p>The module is based on Java 8, so it will not run on Java 8 and 
beyond.</p> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_installation">Installation</h3> 
+   <div class="paragraph"> 
+    <p>To use <em>jndi</em> as a configuration backend you only must add the 
corresponding dependency to your module:</p> 
+   </div> 
+   <div class="listingblock"> 
+    <div class="content"> 
+     <pre class="prettyprint highlight"><code class="language-xml" 
data-lang="xml">&lt;dependency&gt;
   &lt;groupId&gt;org.apache.tamaya.ext&lt;/groupId&gt;
   &lt;artifactId&gt;tamaya-jndi&lt;/artifactId&gt;
   &lt;version&gt;{tamaya_version}&lt;/version&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_the_functionality_provided">The Functionality Provided</h3>
-<div class="paragraph">
-<p>Main artifact is the JNDIConfigSource class, which implements a
-property source based on a JNDI context:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">public class JNDIPropertySource extends BasePropertySource {
+&lt;/dependency&gt;</code></pre> 
+    </div> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_the_functionality_provided">The Functionality Provided</h3> 
+   <div class="paragraph"> 
+    <p>Main artifact is the JNDIConfigSource class, which implements a 
property source based on a JNDI context:</p> 
+   </div> 
+   <div class="listingblock"> 
+    <div class="content"> 
+     <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">public class JNDIPropertySource extends BasePropertySource {
 
     public JNDIPropertySource(String name, Context context);
     public JNDIPropertySource(String name) throws NamingException;
@@ -184,26 +181,20 @@ property source based on a JNDI context:</p>
     public void setScannable(boolean scannable);
 
     [...]
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>By default the property source is <em>non scannable</em>, so a call the 
<code>getProperties()</code>
-will return an empty map instance. After calling 
<code>setScannable(true);</code> a call to
-<code>getProperties()</code> will return a String representation of the JNDI 
tree. Hereby
-leaves of the tree are converted using 
<code>String.valueOf(leaveObject)</code>.</p>
-</div>
-<div class="paragraph">
-<p>This module automatically registers an instance of JNDIConfigSource with a
-default ordinal of 200.</p>
-</div>
-<div class="paragraph">
-<p>You can extend this class or manually instantiate it, e.g. as part of a
-ConfigSourceProvider. If no <code>Context</code> is passed explicitly, a new
-InitialContext is created, without any environment parameters set.</p>
-</div>
-</div>
-</div>
+}</code></pre> 
+    </div> 
+   </div> 
+   <div class="paragraph"> 
+    <p>By default the property source is <em>non scannable</em>, so a call the 
<code>getProperties()</code> will return an empty map instance. After calling 
<code>setScannable(true);</code> a call to <code>getProperties()</code> will 
return a String representation of the JNDI tree. Hereby leaves of the tree are 
converted using <code>String.valueOf(leaveObject)</code>.</p> 
+   </div> 
+   <div class="paragraph"> 
+    <p>This module automatically registers an instance of JNDIConfigSource 
with a default ordinal of 200.</p> 
+   </div> 
+   <div class="paragraph"> 
+    <p>You can extend this class or manually instantiate it, e.g. as part of a 
ConfigSourceProvider. If no <code>Context</code> is passed explicitly, a new 
InitialContext is created, without any environment parameters set.</p> 
+   </div> 
+  </div> 
+ </div> 
 </div></p>
 
                        <hr />
@@ -215,8 +206,8 @@ InitialContext is created, without any environment 
parameters set.</p>
                    <div id="footer">
                      <div class="container">
                        <p class="muted credit">&copy; 2014-<span>2018</span> 
Apache Software Foundation | Mixed with <a 
href="http://getbootstrap.com/";>Bootstrap v3.1.1</a>
-                                                       | Baked with <a 
href="http://jbake.org";>JBake <span>v2.5.1</span></a>
-                                                       at 
<span>2018-05-03</span> |
+                                                       | Baked with <a 
href="http://jbake.org";>JBake <span>v2.6.1</span></a>
+                                                       at 
<span>2018-05-17</span> |
                                                <a 
class="twitter-follow-button" data-show-count="false" 
href="https://twitter.com/tamayaconf";>Follow @tamayaconf</a><script async 
src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
                                                </p>
                                                <p>

http://git-wip-us.apache.org/repos/asf/incubator-tamaya-site/blob/cddd52a8/documentation-new/extensions/mod_jodatime.html
----------------------------------------------------------------------
diff --git a/documentation-new/extensions/mod_jodatime.html 
b/documentation-new/extensions/mod_jodatime.html
index 4d59b34..0574f71 100644
--- a/documentation-new/extensions/mod_jodatime.html
+++ b/documentation-new/extensions/mod_jodatime.html
@@ -125,162 +125,158 @@
                                <h1>Apache Tamaya - Extension: JodaTime</h1>
                        </div>
 
-                       <p><em>2018-04-26</em></p>
+                       <p><em>2018-05-17</em></p>
 
-                       <p><div id="preamble">
-<div class="sectionbody">
-<!-- toc disabled -->
-</div>
-</div>
-<div class="sect1">
-<h2 id="JodaTime">Tamaya JodaTime (Extension Module)</h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>Tamaya <em>JodaTime</em> is an extension module. Refer to the <a 
href="../extensions.html">extensions documentation</a> for further details.</p>
-</div>
-<div class="sect2">
-<h3 id="_what_functionality_this_module_provides">What functionality this 
module provides ?</h3>
-<div class="paragraph">
-<p>Tamaya <em>JodaTime</em> is an extension module to support the usage of <a 
href="http://www.joda.org/joda-time/";>Joda-Time</a>
-in conjunction with Tamaya. Tamaya JodaTime defines some additional property
-converters to use Joda-Time types when accessing configuration.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_installation">Installation</h3>
-<div class="paragraph">
-<p>To support Joda-Time types as configuration values, you only have to add 
the following
-maven dependency to your project:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-listing" 
data-lang="listing">&lt;dependency&gt;
+                       <p><div id="preamble"> 
+ <div class="sectionbody"> 
+  <!-- toc disabled --> 
+ </div> 
+</div> 
+<div class="sect1"> 
+ <h2 id="JodaTime">Tamaya JodaTime (Extension Module)</h2> 
+ <div class="sectionbody"> 
+  <div class="paragraph"> 
+   <p>Tamaya <em>JodaTime</em> is an extension module. Refer to the <a 
href="../extensions.html">extensions documentation</a> for further details.</p> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_what_functionality_this_module_provides">What functionality this 
module provides ?</h3> 
+   <div class="paragraph"> 
+    <p>Tamaya <em>JodaTime</em> is an extension module to support the usage of 
<a href="http://www.joda.org/joda-time/";>Joda-Time</a> in conjunction with 
Tamaya. Tamaya JodaTime defines some additional property converters to use 
Joda-Time types when accessing configuration.</p> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_installation">Installation</h3> 
+   <div class="paragraph"> 
+    <p>To support Joda-Time types as configuration values, you only have to 
add the following maven dependency to your project:</p> 
+   </div> 
+   <div class="listingblock"> 
+    <div class="content"> 
+     <pre class="prettyprint highlight"><code class="language-listing" 
data-lang="listing">&lt;dependency&gt;
   &lt;grooupId&gt;org.apache.tamaya.ext&lt;/groupId&gt;
   &lt;artifactId&gt;tamaya-jodatime&lt;/artifactId&gt;
   &lt;version&gt;{tamaya_version}&lt;/version&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_usage">Usage</h3>
-<div class="paragraph">
-<p>After adding this module to your project you can retrieve
-Joda-Time based values directly from a given configuration.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">Config configuration = ConfigProvider.getConfig();
+&lt;/dependency&gt;</code></pre> 
+    </div> 
+   </div> 
+  </div> 
+  <div class="sect2"> 
+   <h3 id="_usage">Usage</h3> 
+   <div class="paragraph"> 
+    <p>After adding this module to your project you can retrieve Joda-Time 
based values directly from a given configuration.</p> 
+   </div> 
+   <div class="listingblock"> 
+    <div class="content"> 
+     <pre class="prettyprint highlight"><code class="language-java" 
data-lang="java">Config configuration = ConfigProvider.getConfig();
 
-DateTime pit = configuration.get("pointInTime", DateTime.class)</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Currently the following types are supported:</p>
-</div>
-<table class="tableblock frame-all grid-all" style="width: 80%;">
-<colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
-</colgroup>
-<thead>
-<tr>
-<th class="tableblock halign-left valign-top">Joda-Time target type</th>
-<th class="tableblock halign-left valign-top">Supported Input Formats</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td class="tableblock halign-center valign-top" rowspan="12"><p 
class="tableblock">org.joda.time.DateTime org.joda.time.Instant</p></td>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd&#8217;T&#8217;HH:mm:ss.SSSZ</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd&#8217;T&#8217;HH:mm:ss.SSSz</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd&#8217;T&#8217;HH:mm:ss.SSS z</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd&#8217;T&#8217;HH:mm:ssZ</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd&#8217;T&#8217;HH:mm:ssz</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd&#8217;T&#8217;HH:mm:ss z</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd&#8217;T&#8217;HH:mmZ</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd&#8217;T&#8217;HH:mmz</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd&#8217;T&#8217;HH:mm z</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd&#8217;T&#8217;HHZ</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd&#8217;T&#8217;HHz</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd&#8217;T&#8217;HH z</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-center valign-top" rowspan="2"><p 
class="tableblock">org.joda.time.DateTimeZone</p></td>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>[+-]hh:mm</code> (reg.ex.)</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">all 
<em>timezone ids</em> known by Joda-Time.</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-center valign-top" rowspan="3"><p 
class="tableblock">org.joda.time.Duration</p></td>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>PTa.bS</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>PdDThHmMsS</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>ddThh:mm:ss</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-center valign-top" rowspan="2"><p 
class="tableblock">org.joda.time.Period</p></td>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>PyYmMwWdDThHmMsS</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>Pyyyy-mm-ddThh:mm:ss</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-center valign-top" rowspan="4"><p 
class="tableblock">org.joda.time.LocalDate</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock"><code>yyyy 
['-' MM ['-' dd]]</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock"><code>yyyy 
['-' DDD]</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>LocalDateConverter</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock"><code>yyyy 
['-' dd ['-' MM]]</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-center valign-top" rowspan="4"><p 
class="tableblock">org.joda.time.LocalTime</p></td>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>['T']</code> <em>time-element</em></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><em>time-element</em> = HH [<em>minute-element</em>] 
<em>or</em> [<em>fraction</em>]</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><em>minute-element</em> = ':' mm [<em>second-element</em>] 
<em>or</em> [<em>fraction</em>]</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><em>second-element</em> = ':' ss [<em>fraction</em>]</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
+DateTime pit = configuration.get("pointInTime", DateTime.class)</code></pre> 
+    </div> 
+   </div> 
+   <div class="paragraph"> 
+    <p>Currently the following types are supported:</p> 
+   </div> 
+   <table class="tableblock frame-all grid-all" style="width: 80%;"> 
+    <colgroup> 
+     <col style="width: 50%;"> 
+     <col style="width: 50%;"> 
+    </colgroup> 
+    <thead> 
+     <tr> 
+      <th class="tableblock halign-left valign-top">Joda-Time target type</th> 
+      <th class="tableblock halign-left valign-top">Supported Input 
Formats</th> 
+     </tr> 
+    </thead> 
+    <tbody> 
+     <tr> 
+      <td class="tableblock halign-center valign-top" rowspan="12"><p 
class="tableblock">org.joda.time.DateTime org.joda.time.Instant</p></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd’T’HH:mm:ss.SSSZ</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd’T’HH:mm:ss.SSSz</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd’T’HH:mm:ss.SSS z</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd’T’HH:mm:ssZ</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd’T’HH:mm:ssz</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd’T’HH:mm:ss z</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd’T’HH:mmZ</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd’T’HH:mmz</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd’T’HH:mm z</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd’T’HHZ</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd’T’HHz</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy-MM-dd’T’HH z</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-center valign-top" rowspan="2"><p 
class="tableblock">org.joda.time.DateTimeZone</p></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>[+-]hh:mm</code> (reg.ex.)</p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p class="tableblock">all 
<em>timezone ids</em> known by Joda-Time.</p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-center valign-top" rowspan="3"><p 
class="tableblock">org.joda.time.Duration</p></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>PTa.bS</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>PdDThHmMsS</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>ddThh:mm:ss</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-center valign-top" rowspan="2"><p 
class="tableblock">org.joda.time.Period</p></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>PyYmMwWdDThHmMsS</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>Pyyyy-mm-ddThh:mm:ss</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-center valign-top" rowspan="4"><p 
class="tableblock">org.joda.time.LocalDate</p></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy ['-' MM ['-' dd]]</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy ['-' DDD]</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>LocalDateConverter</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>yyyy ['-' dd ['-' MM]]</code></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-center valign-top" rowspan="4"><p 
class="tableblock">org.joda.time.LocalTime</p></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>['T']</code> <em>time-element</em></p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><em>time-element</em> = HH [<em>minute-element</em>] 
<em>or</em> [<em>fraction</em>]</p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><em>minute-element</em> = ':' mm [<em>second-element</em>] 
<em>or</em> [<em>fraction</em>]</p></td> 
+     </tr> 
+     <tr> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><em>second-element</em> = ':' ss 
[<em>fraction</em>]</p></td> 
+     </tr> 
+    </tbody> 
+   </table> 
+  </div> 
+ </div> 
 </div></p>
 
                        <hr />
@@ -292,8 +288,8 @@ DateTime pit = configuration.get("pointInTime", 
DateTime.class)</code></pre>
                    <div id="footer">
                      <div class="container">
                        <p class="muted credit">&copy; 2014-<span>2018</span> 
Apache Software Foundation | Mixed with <a 
href="http://getbootstrap.com/";>Bootstrap v3.1.1</a>
-                                                       | Baked with <a 
href="http://jbake.org";>JBake <span>v2.5.1</span></a>
-                                                       at 
<span>2018-05-03</span> |
+                                                       | Baked with <a 
href="http://jbake.org";>JBake <span>v2.6.1</span></a>
+                                                       at 
<span>2018-05-17</span> |
                                                <a 
class="twitter-follow-button" data-show-count="false" 
href="https://twitter.com/tamayaconf";>Follow @tamayaconf</a><script async 
src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
                                                </p>
                                                <p>

Reply via email to