deltaspike-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r905823 - in /websites/staging/deltaspike/trunk/content: ./ jpa.html
Date Fri, 11 Apr 2014 15:52:09 GMT
Author: buildbot
Date: Fri Apr 11 15:52:08 2014
New Revision: 905823

Log:
Staging update by buildbot for deltaspike

Modified:
    websites/staging/deltaspike/trunk/content/   (props changed)
    websites/staging/deltaspike/trunk/content/jpa.html

Propchange: websites/staging/deltaspike/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Apr 11 15:52:08 2014
@@ -1 +1 @@
-1586690
+1586702

Modified: websites/staging/deltaspike/trunk/content/jpa.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/jpa.html (original)
+++ websites/staging/deltaspike/trunk/content/jpa.html Fri Apr 11 15:52:08 2014
@@ -103,7 +103,7 @@ If you are using features described by t
 <p>The following example shows a simple producer for an <code>EntityManager</code>
and the corresponding dispose-method.
 Producing it as request scoped bean means that the dispose method will be called on finishing
the request.
 As an alternative it's possible to use a special scope called <code>@TransactionScoped</code>
provided by the same DeltaSpike module.</p>
-<p>Producer for the default EntityManager (no EE-Server):</p>
+<p>Producer for the default EntityManager (<strong>no EE-Server</strong>):</p>
 <div class="codehilite"><pre><span class="c1">//...</span>
 <span class="kd">public</span> <span class="kd">class</span> <span
class="nc">EntityManagerProducer</span>
 <span class="o">{</span>
@@ -129,7 +129,7 @@ As an alternative it's possible to use a
 </pre></div>
 
 
-<p>Producer for the default EntityManager (EE-Server):</p>
+<p>Producer for the default EntityManager (<strong>EE-Server</strong>):</p>
 <div class="codehilite"><pre><span class="nd">@ApplicationScoped</span>
 <span class="kd">public</span> <span class="kd">class</span> <span
class="nc">EntityManagerProducer</span>
 <span class="o">{</span>
@@ -392,7 +392,7 @@ So it's possible to catch an exception i
 
 
 <p>As you see the usage is the same. You <strong>don't</strong> have to
use <code>ExtendedEntityManager</code> at the injection point. It's just needed
in the producer-method:</p>
-<p>Producer for the default Extended-<code>EntityManager</code> (no EE-Server):</p>
+<p>Producer for the default Extended-<code>EntityManager</code> (<strong>no
EE-Server</strong>):</p>
 <div class="codehilite"><pre><span class="c1">//...</span>
 <span class="kd">public</span> <span class="kd">class</span> <span
class="nc">ExtendedEntityManagerProducer</span>
 <span class="o">{</span>
@@ -418,7 +418,7 @@ So it's possible to catch an exception i
 </pre></div>
 
 
-<p>Producer for the default Extended-<code>EntityManager</code> (EE-Server):</p>
+<p>Producer for the default Extended-<code>EntityManager</code> (<strong>EE-Server</strong>):</p>
 <div class="codehilite"><pre><span class="nd">@ApplicationScoped</span>
 <span class="kd">public</span> <span class="kd">class</span> <span
class="nc">ExtendedEntityManagerProducer</span>
 <span class="o">{</span>



Mime
View raw message