Author: gpetracek
Date: Fri Apr 11 15:52:02 2014
New Revision: 1586702
URL: http://svn.apache.org/r1586702
Log:
updated content
Modified:
deltaspike/site/trunk/content/jpa.mdtext
Modified: deltaspike/site/trunk/content/jpa.mdtext
URL:
http://svn.apache.org/viewvc/deltaspike/site/trunk/content/jpa.mdtext?rev=1586702&r1=1586701&r2=1586702&view=diff
==============================================================================
--- deltaspike/site/trunk/content/jpa.mdtext (original)
+++ deltaspike/site/trunk/content/jpa.mdtext Fri Apr 11 15:52:02 2014
@@ -38,7 +38,7 @@ The following example shows a simple pro
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
`@TransactionScoped` provided by the same DeltaSpike module.
-Producer for the default EntityManager (no EE-Server):
+Producer for the default EntityManager (**no EE-Server**):
:::java
//...
@@ -64,7 +64,7 @@ Producer for the default EntityManager (
}
}
-Producer for the default EntityManager (EE-Server):
+Producer for the default EntityManager (**EE-Server**):
:::java
@ApplicationScoped
@@ -339,7 +339,7 @@ Usage of a simple `ExtendedEntityManager
As you see the usage is the same. You **don't** have to use
`ExtendedEntityManager` at the injection point. It's just needed in the
producer-method:
-Producer for the default Extended-`EntityManager` (no EE-Server):
+Producer for the default Extended-`EntityManager` (**no EE-Server**):
:::java
//...
@@ -366,7 +366,7 @@ Producer for the default Extended-`Entit
}
-Producer for the default Extended-`EntityManager` (EE-Server):
+Producer for the default Extended-`EntityManager` (**EE-Server**):
:::java
