You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@deltaspike.apache.org by bu...@apache.org on 2016/03/17 00:28:15 UTC
svn commit: r982962 - in /websites/staging/deltaspike/trunk/content: ./
staging/external.html
Author: buildbot
Date: Wed Mar 16 23:28:15 2016
New Revision: 982962
Log:
Staging update by buildbot for deltaspike
Modified:
websites/staging/deltaspike/trunk/content/ (props changed)
websites/staging/deltaspike/trunk/content/staging/external.html
Propchange: websites/staging/deltaspike/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Mar 16 23:28:15 2016
@@ -1 +1 @@
-1731579
+1735344
Modified: websites/staging/deltaspike/trunk/content/staging/external.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/staging/external.html (original)
+++ websites/staging/deltaspike/trunk/content/staging/external.html Wed Mar 16 23:28:15 2016
@@ -284,6 +284,22 @@ table.CodeRay td.code>pre{padding:0}
<div class="paragraph">
<p><strong>CDI@Work (chapter about DeltaSpike):</strong> <a href="http://cdiatwork.irian.at/" class="bare">http://cdiatwork.irian.at/</a></p>
</div>
+<div class="olist lowerroman">
+<ol class="lowerroman" type="i">
+<li>
+<p>is a free online book about CDI as well as Apache DeltaSpike.
+It covers basic information about CDI and DeltaSpike up to more advanced use-cases.
+An example for the latter is a type-safe configuration (interface-only)
+which allows you to resolve the configured values even from dynamic config-sources like a database and
+store them in a custom Config-Scoped cache which can be refreshed via CDI-events or a CRON based task or manually via JMX.</p>
+</li>
+</ol>
+</div>
+<div class="paragraph">
+<p>The <a href="https://github.com/CDIatWork/">GitHub account</a> contains repositories e.g. for the sample application called IdeaFork.
+The commit-history follows the steps in the book. In most cases every commit translates to one step in the book.
+(Chapters are released once they are ready.)</p>
+</div>
</div>
</div>
<div class="sect1">
@@ -385,11 +401,14 @@ The repository contains every step (one
</div>
</div>
<div class="sect2">
-<h3 id="__preview_ideafork_lite">[Preview] IdeaFork (lite)</h3>
+<h3 id="_ideafork_lite">IdeaFork (lite)</h3>
<div class="paragraph">
-<p>This example will be based on IdeaFork (full),
+<p>This example is based on IdeaFork (full),
but without some indirections which were needed to demonstrate different features of CDI and DeltaSpike (in a simple Application).</p>
</div>
+<div class="paragraph">
+<p><strong>Source code (beta - work in progress):</strong> <a href="https://github.com/CDIatWork/IdeaForkLite_Beta" class="bare">https://github.com/CDIatWork/IdeaForkLite_Beta</a></p>
+</div>
</div>
<div class="sect2">
<h3 id="_confess_2012_workshop_demo">Confess 2012 Workshop Demo</h3>
@@ -614,7 +633,7 @@ but without some indirections which were
<li><a href="#_examples">Examples</a>
<ul class="sectlevel2">
<li><a href="#_ideafork_full">IdeaFork (full)</a></li>
-<li><a href="#__preview_ideafork_lite">[Preview] IdeaFork (lite)</a></li>
+<li><a href="#_ideafork_lite">IdeaFork (lite)</a></li>
<li><a href="#_confess_2012_workshop_demo">Confess 2012 Workshop Demo</a></li>
<li><a href="#_fullstack_ee6_with_deltaspike">Fullstack EE6+ with DeltaSpike</a></li>
<li><a href="#_fullstack_codi_to_deltaspike">Fullstack CODI to DeltaSpike</a></li>