You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by db...@apache.org on 2018/12/25 04:39:00 UTC
svn commit: r1849711 [9/11] - in /tomee/site/trunk/content: ./ community/
community/contributing/ latest/docs/ latest/docs/application-composer/
latest/docs/developer/json/
latest/docs/developer/testing/applicationcomposer/
latest/docs/developer/testin...
Modified: tomee/site/trunk/content/tomee-8.0/docs/local-client-injection.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/docs/local-client-injection.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/docs/local-client-injection.html (original)
+++ tomee/site/trunk/content/tomee-8.0/docs/local-client-injection.html Tue Dec 25 04:38:58 2018
@@ -98,15 +98,15 @@
<div id="preamble">
<div class="sectionbody">
<div class="paragraph">
-<p>The <em>@LocalClient</em> annotation (org.apache.openejb.api.LocalClient) is an
+<p>The <em>`@LocalClient</em>` annotation (org.apache.openejb.api.LocalClient) is an
innovation that crosses concepts of an Java EE Application Client with a
plain Java SE client. This particular annotation is focused on clients
of an Embeddable EJB container, i.e. local clients. There is another
-annotation in development called @RemoteClient that will be focused on
+annotation in development called <code>@RemoteClient</code> that will be focused on
remote clients; clients running outside the vm the container runs.</p>
</div>
<div class="paragraph">
-<p>Any clients annotated with @LocalClient will be scanned at deployment
+<p>Any clients annotated with <code>@LocalClient</code> will be scanned at deployment
time for usage of injection-related annotations. The references in the
@LocalClient will be processed with the application just as if the class
was a Java EE Application Client module, but with a few slight
@@ -118,13 +118,13 @@ differences:</p>
<p>Declaring field/method injection points as 'static' is not required</p>
</li>
<li>
-<p>References to EntityManagers via @PersistenceContext are allowed</p>
+<p>References to EntityManagers via <code>@PersistenceContext</code> are allowed</p>
</li>
<li>
-<p>References to local business interfaces via @EJB is allowed</p>
+<p>References to local business interfaces via <code>@EJB</code> is allowed</p>
</li>
<li>
-<p>References to UserTransaction via @Resource is allowed</p>
+<p>References to UserTransaction via <code>@Resource</code> is allowed</p>
</li>
</ol>
</div>
@@ -134,7 +134,7 @@ are not required to use any special pack
to run the client. Your client can be a Unit Test or any plain java code
that needs to pull objects from the Embedded EJB container. Classes with
@LocalClient can be placed in a Client module or an EJB module. A given
-module may have as many classes annotated with @LocalClient as it
+module may have as many classes annotated with <code>@LocalClient</code> as it
wishes.</p>
</div>
</div>
@@ -172,7 +172,7 @@ public class MoviesTest extends TestCase
</div>
<h1 id="_discovery" class="sect0">Discovery</h1>
<div class="paragraph">
-<p>All EJB modules are scanned for @LocalClient classes, even if those EJB
+<p>All EJB modules are scanned for <code>@LocalClient</code> classes, even if those EJB
Modules are inside .war files as with the
<a href="collapsed-ear.html">Collapsed EAR</a> . As well any modules that
contain a META-INF/application-client.xml file will be scanned for
@@ -180,14 +180,14 @@ contain a META-INF/application-client.xm
</div>
<div class="paragraph">
<p>If you see the following error message and are absolutely sure the
-module containing your @LocalClient class is being properly identified
+module containing your <code>@LocalClient</code> class is being properly identified
as an EJB module or a Client module, than it is possible you are seeing
some classloading issues.</p>
</div>
<div class="paragraph">
<p>{panel} javax.naming.NamingException: Unable to find injection
meta-data for org.superbiz.MyClient. Ensure that class was annotated
-with @org.apache.openejb.api.LocalClient and was successfully discovered
+with <code>@org</code>.apache.openejb.api.LocalClient and was successfully discovered
and deployed. {panel}</p>
</div>
<div class="paragraph">
Modified: tomee/site/trunk/content/tomee-8.0/docs/lookup-of-other-ejbs-example.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/docs/lookup-of-other-ejbs-example.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/docs/lookup-of-other-ejbs-example.html (original)
+++ tomee/site/trunk/content/tomee-8.0/docs/lookup-of-other-ejbs-example.html Tue Dec 25 04:38:58 2018
@@ -98,7 +98,7 @@
<h1 id="_overview" class="sect0">Overview</h1>
<div class="paragraph">
<p>This example shows how to configure JNDI to lookup other EJBs using
-either the <em>@EJB</em> annotation or the <em>ejb-jar.xml</em> deployment descriptor.</p>
+either the <em>`@EJB</em>` annotation or the <em>ejb-jar.xml</em> deployment descriptor.</p>
</div>
<div class="paragraph">
<p>There are a couple interesting aspects in this example intended to flush
@@ -181,7 +181,7 @@ does not necessarily identify the exact
</ul>
</div>
<div class="paragraph">
-<p>To illustrate all of this, we have two simple @Stateless beans,
+<p>To illustrate all of this, we have two simple <code>@Stateless</code> beans,
<em>RedBean</em> and <em>BlueBean</em>. Both implement the same business local
interface, <em>Friend</em>. Both <em>RedBean</em> and <em>BlueBean</em> define
<em>java:comp/env/myFriend</em> differently which is allowed as <em>java:comp</em> is
@@ -196,10 +196,10 @@ business local interface <em>Friend</em>
\{snippet:id=code|url=openejb3/examples/lookup-of-ejbs/src/main/java/org/superbiz/ejblookup/Friend.java|lang=java}</p>
</div>
<div class="paragraph">
-<p>The key items in the above are the following: - <em>@EJB</em> has been used at
+<p>The key items in the above are the following: - <em>`@EJB</em>` has been used at
the <em>class level</em> to declare <em>myFriend</em> in the <em>java:comp/env</em> namespace
of each EJB - because both beans share the <em>same interface</em>, <em>Friend</em>,
-we need to add <strong>beanName</strong> to the <em>@EJB</em> usage to specify the exact EJB
+we need to add <strong>beanName</strong> to the <em>`@EJB</em>` usage to specify the exact EJB
we want - for <em>BlueBean</em> the <em>java:comp/env/myFriend</em> name has been
configured to point to <em>RedBean</em> - for <em>RedBean</em> the
<em>java:comp/env/myFriend</em> name has been configured to point to <em>BlueBean</em></p>
Modified: tomee/site/trunk/content/tomee-8.0/docs/new-in-openejb-3.0.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/docs/new-in-openejb-3.0.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/docs/new-in-openejb-3.0.html (original)
+++ tomee/site/trunk/content/tomee-8.0/docs/new-in-openejb-3.0.html Tue Dec 25 04:38:58 2018
@@ -162,7 +162,7 @@ against the same data. Everything is ult
<h2 id="_extended_dependency_injection">Extended Dependency Injection</h2>
<div class="sectionbody">
<div class="paragraph">
-<p>Dependency Injection in EJB 3.0 via @Resource is largely limited to
+<p>Dependency Injection in EJB 3.0 via <code>@Resource</code> is largely limited to
objects provided by the container, such as DataSources, JMS Topics and
Queues. It is possible for you to supply your own configuration
information for injection, but standard rules allow for only data of
@@ -206,7 +206,7 @@ Integer, etc. This is a very big burden
cost you 5 lines of xml and the complication of having to figure out how
to add you bean declaration in xml as an override of an existing bean
and not accidentally as a new bean. All this can be very painful when
-all you want is to supply the value of a few @Resource String fields in
+all you want is to supply the value of a few <code>@Resource</code> String fields in
you bean class.</p>
</div>
<div class="paragraph">
@@ -265,7 +265,7 @@ failures.</p>
<p>As usual validation failures (non-compliant issues with your
application) are printed out in complier-style "all-at-once" output
allowing you to see and fix all your issues in one go. For example, if
-you have 10 @PersistenceContext annotations that reference an invalid
+you have 10 <code>@PersistenceContext</code> annotations that reference an invalid
persistence unit, you get all 10 errors on the <em>first</em> deploy rather
than one failure on the first deploy with 9 more failed deployments to
go.</p>
Modified: tomee/site/trunk/content/tomee-8.0/docs/persistence-context.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/docs/persistence-context.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/docs/persistence-context.html (original)
+++ tomee/site/trunk/content/tomee-8.0/docs/persistence-context.html Tue Dec 25 04:38:58 2018
@@ -129,7 +129,7 @@ public class MyBean implements MyInterfa
</div>
<h1 id="_via_xml" class="sect0">Via xml</h1>
<div class="paragraph">
-<p>The above @PersistenceContext annotation usage is 100% equivalent to the
+<p>The above <code>@PersistenceContext</code> annotation usage is 100% equivalent to the
following xml.</p>
</div>
<div class="listingblock">
Modified: tomee/site/trunk/content/tomee-8.0/docs/persistence-unit-ref.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/docs/persistence-unit-ref.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/docs/persistence-unit-ref.html (original)
+++ tomee/site/trunk/content/tomee-8.0/docs/persistence-unit-ref.html Tue Dec 25 04:38:58 2018
@@ -99,7 +99,7 @@
<div class="sectionbody">
<div class="paragraph">
<p>Both lookup and injection of an
-EntityManagerFactory can be configured via the @PersistenceUnit
+EntityManagerFactory can be configured via the <code>@PersistenceUnit</code>
annotation or in xml. Annotations and xml have equal function in both
lookup and injection.</p>
</div>
@@ -140,7 +140,7 @@ public class MyBean implements MyInterfa
<h2 id="_via_xml">Via xml</h2>
<div class="sectionbody">
<div class="paragraph">
-<p>The above @PersistenceUnit annotation usage is 100% equivalent to the
+<p>The above <code>@PersistenceUnit</code> annotation usage is 100% equivalent to the
following xml.</p>
</div>
<div class="listingblock">
@@ -188,7 +188,7 @@ public class MyBean implements MyInterfa
</div>
<h1 id="_via_xml_2" class="sect0">Via xml</h1>
<div class="paragraph">
-<p>The above @PersistenceUnit annotation usage is 100% equivalent to the
+<p>The above <code>@PersistenceUnit</code> annotation usage is 100% equivalent to the
following xml.</p>
</div>
<div class="listingblock">
Modified: tomee/site/trunk/content/tomee-8.0/docs/resource-injection.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/docs/resource-injection.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/docs/resource-injection.html (original)
+++ tomee/site/trunk/content/tomee-8.0/docs/resource-injection.html Tue Dec 25 04:38:58 2018
@@ -99,7 +99,7 @@
<div class="sectionbody">
<div class="paragraph">
<p>This example demonstrates the use of the injection of environment
-entries using <strong>@Resource</strong> annotation.</p>
+entries using <strong><code>@Resource</code></strong> annotation.</p>
</div>
<div class="paragraph">
<p>The EJB 3.0 specification (<em>EJB Core Contracts and Requirements</em>)
@@ -120,11 +120,11 @@ method that is called to inject the envi
property name (not the method name) is used as the default JNDI name.</em></p>
</div>
<div class="paragraph">
-<p>The <em>PurchaseOrderBean</em> class shows use of field-level <strong>@Resource</strong>
+<p>The <em>PurchaseOrderBean</em> class shows use of field-level <strong><code>@Resource</code></strong>
annotation.</p>
</div>
<div class="paragraph">
-<p>The <em>InvoiceBean</em> class shows the use of method-level <strong>@Resource</strong>
+<p>The <em>InvoiceBean</em> class shows the use of method-level <strong><code>@Resource</code></strong>
annotation.</p>
</div>
<div class="paragraph">
Modified: tomee/site/trunk/content/tomee-8.0/docs/resource-ref-for-datasource.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/docs/resource-ref-for-datasource.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/docs/resource-ref-for-datasource.html (original)
+++ tomee/site/trunk/content/tomee-8.0/docs/resource-ref-for-datasource.html Tue Dec 25 04:38:58 2018
@@ -130,7 +130,7 @@ public class MyDataSourceRefBean impleme
<h2 id="_via_xml">Via xml</h2>
<div class="sectionbody">
<div class="paragraph">
-<p>The above @Resource annotation usage is 100% equivalent to the following
+<p>The above <code>@Resource</code> annotation usage is 100% equivalent to the following
xml.</p>
</div>
<div class="listingblock">
Modified: tomee/site/trunk/content/tomee-8.0/docs/security-annotations.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/docs/security-annotations.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/docs/security-annotations.html (original)
+++ tomee/site/trunk/content/tomee-8.0/docs/security-annotations.html Tue Dec 25 04:38:58 2018
@@ -236,7 +236,7 @@ public class OpenSourceProjectBean imple
<h2 id="_declareroles">DeclareRoles</h2>
<div class="sectionbody">
<div class="paragraph">
-<p>You need to update the @DeclareRoles when referencing roles via
+<p>You need to update the <code>@DeclareRoles</code> when referencing roles via
isCallerInRole(roleName).</p>
</div>
<div class="listingblock">
@@ -348,7 +348,7 @@ public class OpenSourceProjectBean imple
<h2 id="_permitall">PermitAll</h2>
<div class="sectionbody">
<div class="paragraph">
-<p>When annotating a bean class with @RolesAllowed, the @PermitAll
+<p>When annotating a bean class with <code>@RolesAllowed</code>, the <code>@PermitAll</code>
annotation becomes very useful on individual methods to open them back
up again.</p>
</div>
@@ -396,7 +396,7 @@ public class OpenSourceProjectBean imple
<h2 id="_denyall">DenyAll</h2>
<div class="sectionbody">
<div class="paragraph">
-<p>The @DenyAll annotation can be used to restrict business interface
+<p>The <code>@DenyAll</code> annotation can be used to restrict business interface
access from anyone, logged in or not. The method is still invokable from
within the bean class itself.</p>
</div>
@@ -454,7 +454,7 @@ public class OpenSourceProjectBean imple
and most callbacks.</p>
</div>
<div class="paragraph">
-<p>The following usages of @RolesAllowed have no effect.</p>
+<p>The following usages of <code>@RolesAllowed</code> have no effect.</p>
</div>
<div class="listingblock">
<div class="content">
Modified: tomee/site/trunk/content/tomee-8.0/docs/singleton-beans.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/docs/singleton-beans.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/docs/singleton-beans.html (original)
+++ tomee/site/trunk/content/tomee-8.0/docs/singleton-beans.html Tue Dec 25 04:38:58 2018
@@ -97,8 +97,8 @@
<div class="col-md-12">
<h1 id="_singleton_overview_for_the_first_time_in_years_ejb_has_a_new" class="sect0">Singleton Overview For the first time in years EJB has a new</h1>
<div class="paragraph">
-<p>bean type, the <em>@Singleton</em>. In my opinion, the javax.ejb.Singleton will
-replace a lot of what people are using @Stateless for today.</p>
+<p>bean type, the <em>`@Singleton</em>`. In my opinion, the javax.ejb.Singleton will
+replace a lot of what people are using <code>@Stateless</code> for today.</p>
</div>
<div class="paragraph">
<p>The Singleton is essentially what you get if you take a Stateless bean
@@ -107,13 +107,13 @@ exactly one instance of the Singleton be
be invoked concurrently by multiple threads, like a servlet. It can do
everything a Stateless can do such as support local and remote business
interfaces, web services, security, transactions, and more.
-Additionally, the Singleton can have its @PostConstruct method called
-with the application starts up and its @PreDestroy method called when
+Additionally, the Singleton can have its <code>@PostConstruct</code> method called
+with the application starts up and its <code>@PreDestroy</code> method called when
the application shuts down. This allows it to serve as an application
lifecycle listener which is something only Servlets could do before. It
-has an <em>@Startup</em> annotation which is similar in concept to the servlet
+has an <em>`@Startup</em>` annotation which is similar in concept to the servlet
, but unlike servlets it doesn’t take a number as an argument. Instead,
-you can use an <em>@DependsOn</em> annotation to say which other Singletons you
+you can use an <em>`@DependsOn</em>` annotation to say which other Singletons you
need and the container will ensure they start before you.</p>
</div>
<div class="paragraph">
@@ -155,15 +155,15 @@ exclusive lock on the bean for the durat
other threads for that or any other method must wait.</p>
</div>
<div class="paragraph">
-<p>The second option is a "read" lock, annotated as <em>@Lock(READ)</em>. The read
+<p>The second option is a "read" lock, annotated as <em>`@Lock`(READ)</em>. The read
lock allows full concurrent access to the methods (assuming no write
locks are held). The default mode of "write" essentially makes your bean
a single-threaded bean, which is very slow. The more conservative
@Lock(WRITE) was chosen as the default as this is how all the other bean
types work (only a single thread may access a bean instance at any given
time). Those that are aware of how to handle concurrent access can
-easily put @Lock(READ) on their bean class, thus changing the default,
-and then @Lock(WRITE) on specific methods if needed.</p>
+easily put <code>@Lock</code>(READ) on their bean class, thus changing the default,
+and then <code>@Lock</code>(WRITE) on specific methods if needed.</p>
</div>
<div class="paragraph">
<p>The locking modes of Container-Managed Concurrency map directly to the
@@ -221,7 +221,7 @@ downgrading, and</p>
<div class="sect3">
<h4 id="_acquiring_the_lock">Acquiring the Lock</h4>
<div class="paragraph">
-<p>The <em>@AccessTimetout</em> annotation can configure how long a thread will
+<p>The <em>`@AccessTimetout</em>` annotation can configure how long a thread will
wait to acquire the read or write lock. This annotation can be used on
the bean class or individual methods. The annotation maps directly to
the
@@ -265,7 +265,7 @@ interface.</p>
<div class="sect3">
<h4 id="_default_timeout">Default Timeout</h4>
<div class="paragraph">
-<p>The default value of <em>@AccessTimeout</em> annotation is vendor specific. In
+<p>The default value of <em>`@AccessTimeout</em>` annotation is vendor specific. In
OpenEJB it defaults to the value of the <em>AccessTimeout</em> property which
can be configured in many different scopes. Here is the order of
preference:</p>
@@ -303,17 +303,17 @@ hour and 23 minutes and 17 seconds" see
<h2 id="_startup_and_startup_ordering">Startup and Startup Ordering</h2>
<div class="sectionbody">
<div class="paragraph">
-<p>Singletons have an <em>@Startup</em> annotation which can be applied to the
+<p>Singletons have an <em>`@Startup</em>` annotation which can be applied to the
bean class. When used, the Container will instantiate the Singleton
instance <em>eagerly</em> when the application starts up, otherwise the
Container will instantiate the Singleton instance <em>lazily</em> when the bean
is first accessed.</p>
</div>
<div class="paragraph">
-<p>If one Singleton refers to another Singleton in the @PostConstruct or
+<p>If one Singleton refers to another Singleton in the <code>@PostConstruct</code> or
@PreDestroy method, there must be some measure taken to ensure the other
Singleton exists and is started. This sort of ordering is achieved with
-the <em>@DependsOn</em> annotation which can be used to list the names of
+the <em>`@DependsOn</em>` annotation which can be used to list the names of
Singleton beans that must be started before the Singleton bean using the
annotation.</p>
</div>
@@ -327,23 +327,23 @@ public class SingletonA {
</div>
</div>
<div class="paragraph">
-<p>Circular references are not supported. If BeanA uses @DependsOn to point
-to BeanB and BeanB also uses @DependsOn to point at BeanA, the result is
+<p>Circular references are not supported. If BeanA uses <code>@DependsOn</code> to point
+to BeanB and BeanB also uses <code>@DependsOn</code> to point at BeanA, the result is
a deployment exception. Be aware that circular references can happen in
less trivial ways such as A referring to B which refers to C which
refers to D which refers back to A. We will detect and print all
circular dependencies (called circuits) at deploy time.</p>
</div>
<div class="paragraph">
-<p>Note that @DependsOn is only required (and should only be used) if a
-Singleton <em>uses</em> another Singleton in its @PostConstruct method or
+<p>Note that <code>@DependsOn</code> is only required (and should only be used) if a
+Singleton <em>uses</em> another Singleton in its <code>@PostConstruct</code> method or
@PreDestroy method. Simply having a reference to another Singleton and
-using it in other business methods does not require an @DependsOn
-declaration. The @DependsOn allows the Container to calculate the
+using it in other business methods does not require an <code>@DependsOn</code>
+declaration. The <code>@DependsOn</code> allows the Container to calculate the
correct startup order and shutdown order so that it can guarantee the
-Singletons you need are available in your @PostConstruct or @PreDestroy
+Singletons you need are available in your <code>@PostConstruct</code> or <code>@PreDestroy</code>
methods. All Singletons will automatically be available to your business
-methods regardless if @DependsOn is used. Because of the greater chance
+methods regardless if <code>@DependsOn</code> is used. Because of the greater chance
of creating circular dependencies, it is better not to use the
@DependsOn annotation "just in case" and should only be used when truly
needed.</p>
Modified: tomee/site/trunk/content/tomee-8.0/docs/spring-and-openejb-3.0.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/docs/spring-and-openejb-3.0.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/docs/spring-and-openejb-3.0.html (original)
+++ tomee/site/trunk/content/tomee-8.0/docs/spring-and-openejb-3.0.html Tue Dec 25 04:38:58 2018
@@ -184,8 +184,8 @@ that Spring creates, here’s one te
<div class="paragraph">
<p>Let’s say you have a persistence unit called "<em>OrangeUnit</em>" declared in
a persistence.xml file. One way to get the related <em>EntityManager</em>
-created by OpenEJB is to do as follows. Create an @Stateless bean with
-an @PersistenceContext ref in it, then use a factory bean to look it up,
+created by OpenEJB is to do as follows. Create an <code>@Stateless</code> bean with
+an <code>@PersistenceContext</code> ref in it, then use a factory bean to look it up,
pull the EntityManager out and return it</p>
</div>
<div class="paragraph">
Modified: tomee/site/trunk/content/tomee-8.0/docs/spring-ejb-and-jpa.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/docs/spring-ejb-and-jpa.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/docs/spring-ejb-and-jpa.html (original)
+++ tomee/site/trunk/content/tomee-8.0/docs/spring-ejb-and-jpa.html Tue Dec 25 04:38:58 2018
@@ -127,7 +127,7 @@ of Movies. The basic object layout is as
<p>@Stateless</p>
</div>
<div class="paragraph">
-<p>Shows the use of @Resource to have Spring beans injected. Specifically,
+<p>Shows the use of <code>@Resource</code> to have Spring beans injected. Specifically,
the <em>Theaters</em> Spring bean</p>
</div>
<div class="paragraph">
@@ -224,10 +224,10 @@ And finally our Spring beans.
{title= Don’t forget}
\{snippet:id=annotations|url=openejb3/examples/spring-integration/src/main/resources/movies.xml|lang=xml}
It allows various annotations to be detected in bean classes: Spring’s
-@Required and @Autowired, as well as JSR 250’s @PostConstruct,
-@PreDestroy and @Resource (if available), JAX-WS’s @WebServiceRef (if
-available), EJB3’s @EJB (if available), and JPA’s @PersistenceContext
-and @PersistenceUnit (if available). Alternatively, you may choose to
+@Required and <code>@Autowired</code>, as well as JSR 250’s <code>@PostConstruct</code>,
+@PreDestroy and <code>@Resource</code> (if available), JAX-WS’s <code>@WebServiceRef</code> (if
+available), EJB3’s <code>@EJB</code> (if available), and JPA’s <code>@PersistenceContext</code>
+and <code>@PersistenceUnit</code> (if available). Alternatively, you may choose to
activate the individual BeanPostProcessors for those annotations.
{note}</p>
</div>
Modified: tomee/site/trunk/content/tomee-8.0/docs/tomcat-object-factory.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/docs/tomcat-object-factory.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/docs/tomcat-object-factory.html (original)
+++ tomee/site/trunk/content/tomee-8.0/docs/tomcat-object-factory.html Tue Dec 25 04:38:58 2018
@@ -102,7 +102,7 @@ article "OpenEJB: EJB for Tomcat"</a> is
</div>
<div class="paragraph">
<p>As of OpenEJB 3.0 references from Servlets to EJBs happen automatically
-with usage of the [@EJB
+with usage of the [<code>@EJB</code>
annotation](openejbx30:injection-of-other-ejbs-example.html) in the
Servlet, Filter or Listener or with the or declared in the web.xml.</p>
</div>
Modified: tomee/site/trunk/content/tomee-8.0/docs/tomee-and-security.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/docs/tomee-and-security.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/docs/tomee-and-security.html (original)
+++ tomee/site/trunk/content/tomee-8.0/docs/tomee-and-security.html Tue Dec 25 04:38:58 2018
@@ -137,7 +137,7 @@ application</a> , all we would need to d
<p>Add some users to the tomcat-users.xml file<br></p>
</li>
<li>
-<p>Add the necessary @DefineRoles and @RolesAllowed annotations on
+<p>Add the necessary <code>@DefineRoles</code> and <code>@RolesAllowed</code> annotations on
MoviesImpl<br></p>
</li>
<li>
Modified: tomee/site/trunk/content/tomee-8.0/docs/transaction-annotations.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/docs/transaction-annotations.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/docs/transaction-annotations.html (original)
+++ tomee/site/trunk/content/tomee-8.0/docs/transaction-annotations.html Tue Dec 25 04:38:58 2018
@@ -102,11 +102,11 @@
for an example of how to use and test EJB transaction attributes</em></p>
</div>
<div class="paragraph">
-<p>The <em>javax.ejb.TransactionAttribute</em> annotation (@TransactionAttribute)
+<p>The <em>javax.ejb.TransactionAttribute</em> annotation (<code>@TransactionAttribute</code>)
can be applied to a bean class or it’s methods.</p>
</div>
<div class="paragraph">
-<p>Usage of the @TransactionAttribute requires you to specify one of six
+<p>Usage of the <code>@TransactionAttribute</code> requires you to specify one of six
different transaction attribute types defined via the
javax.ejb.TransactionAttributeType enum.</p>
</div>
@@ -364,7 +364,7 @@ public static class MyBean implements My
methods and most callbacks.</p>
</div>
<div class="paragraph">
-<p>The following usages of @TransactionAttribute have no effect.</p>
+<p>The following usages of <code>@TransactionAttribute</code> have no effect.</p>
</div>
<div class="listingblock">
<div class="content">
Modified: tomee/site/trunk/content/tomee-8.0/examples/access-timeout-meta.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/examples/access-timeout-meta.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/examples/access-timeout-meta.html (original)
+++ tomee/site/trunk/content/tomee-8.0/examples/access-timeout-meta.html Tue Dec 25 04:38:58 2018
@@ -95,16 +95,55 @@
<div class="row">
<div class="col-md-12">
- <p>Any annotation that takes parameters can benefit from meta-annotations. Here we see how <code>@AccessTimeout</code> can be far more understandable and manageable through meta-annotations. We'll use the <a href="../access-timeout/README.html">access-timeout</a> example as our use-case.</p>
-<p>The value of the parameters supplied to <code>@AccessTimeout</code> have a dramatic affect on what that annotation actually does. Moreover, <code>@AccessTimeout</code> has one of those designs where <code>-1</code> and <code>0</code> have signifcantly different meanings. One means "wait forever", the other means "never wait". Only a lucky few can remember which is which on a daily basis. For the rest of us it is a constant source of bugs.</p>
-<p>Meta-Annotations to the rescue!</p>
-<h1>Creating the Meta-Annotations</h1>
-<p>As a matter of best-practices, we will put our meta-annotations in a package called <code>api</code>, for this example that gives us <code>org.superbiz.accesstimeout.api</code>. The package <code>org.superbiz.api</code> would work just as well.</p>
-<p>The basic idea is to have a package where "approved' annotations are used and to prohibit usage of the non-meta versions of the annotations. All the real configuration will then be centralized in the <code>api</code> package and changes to timeout values will be localized to that package and automatically be reflected throuhout the application.</p>
-<p>An interesting side-effect of this approach is that if the <code>api</code> package where the meta-annotation definitions exist is kept in a separate jar as well, then one can effectively change the configuration of an entire application by simply replacing the <code>api</code> jar.</p>
-<h2>@Metatype <small>The "root" Meta-Annotation</small></h2>
-<p>As with all meta-annotation usage, you first need to create your own "root" meta-annotation. This is as easy as creating an annotation named <code>Metatype</code> that is annotated with itself and has <code>ElementType.ANNOTATION_TYPE</code> as its target.</p>
-<pre><code>package org.superbiz.accesstimeout.api;
+ <div class="sect1">
+<h2 id="_introduction">Introduction</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Any annotation that takes parameters can benefit from meta-annotations. Here we see how <code>@AccessTimeout</code> can be far more understandable and manageable through meta-annotations.
+We’ll use the [access-timeout](../access-timeout/README.html) example as our use-case.</p>
+</div>
+<div class="paragraph">
+<p>The value of the parameters supplied to <code>@AccessTimeout</code> have a dramatic affect on what that annotation actually does. Moreover, <code>@AccessTimeout</code> has one of those designs
+where <code>-1</code> and <code>0</code> have signifcantly different meanings. One means "wait forever", the other means "never wait". Only a lucky few can remember which is which on a daily basis.
+For the rest of us it is a constant source of bugs.</p>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+Meta-Annotations to the rescue!
+</td>
+</tr>
+</table>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="__strong_em_creating_the_meta_annotations_em_strong"><strong><em>Creating the Meta-Annotations</em></strong></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>As a matter of best-practices, we will put our meta-annotations in a package called <code>api</code>, for this example that gives us <code>org.superbiz.accesstimeout.api</code>. The package <code>org.superbiz.api</code> would work just as well.</p>
+</div>
+<div class="paragraph">
+<p>The basic idea is to have a package where "approved' annotations are used and to prohibit usage of the non-meta versions of the annotations. All the real configuration will
+then be centralized in the <code>api</code> package and changes to timeout values will be localized to that package and automatically be reflected throuhout the application.</p>
+</div>
+<div class="paragraph">
+<p>An interesting side-effect of this approach is that if the <code>api</code> package where the meta-annotation definitions exist is kept in a separate jar as well, then one can effectively
+change the configuration of an entire application by simply replacing the <code>api</code> jar.</p>
+</div>
+<div class="sect2">
+<h3 id="__metatype_span_class_small_the_root_meta_annotation_span">@Metatype <span class="small">The "root" Meta-Annotation</span></h3>
+<div class="paragraph">
+<p>As with all meta-annotation usage, you first need to create your own "root" meta-annotation. This is as easy as creating an annotation
+named <code>Metatype</code> that is annotated with itself and has <code>ElementType.ANNOTATION_TYPE</code> as its target.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">package org.superbiz.accesstimeout.api;
import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
@@ -115,12 +154,23 @@ import java.lang.annotation.Target;
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.ANNOTATION_TYPE)
public @interface Metatype {
-}
-</code></pre>
-<h2>@AwaitNever</h2>
-<p>When the <code>@AccessTimeout</code> annotation has the value of <code>0</code> that has the implication that one should never wait to access the bean. If the bean is busy, the caller will immediately receive an <code>ConcurrentAccessException</code>. This is hard to remember and definitely not self-documenting for those that never knew the details.</p>
-<p>To create a meta-annotation version of <code>@AccessTimeout(0)</code> we simply need to think of a good annotation name, create that annotation, and annotate it with both <code>@AccessTimeout</code> and <code>@Metatype</code></p>
-<pre><code>package org.superbiz.accesstimeout.api;
+}</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="__awaitnever">@AwaitNever</h3>
+<div class="paragraph">
+<p>When the <code>@AccessTimeout</code> annotation has the value of <code>0</code> that has the implication that one should never wait to access the bean. If the bean is busy, the caller will immediately
+receive an <code>ConcurrentAccessException</code>. This is hard to remember and definitely not self-documenting for those that never knew the details.</p>
+</div>
+<div class="paragraph">
+<p>To create a meta-annotation version of <code>@AccessTimeout(0)</code> we simply need to think of a good annotation name, create that annotation, and annotate it with both <code>@AccessTimeout</code>
+and <code>@Metatype</code></p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">package org.superbiz.accesstimeout.api;
import javax.ejb.AccessTimeout;
import java.lang.annotation.ElementType;
@@ -134,13 +184,26 @@ import java.lang.annotation.Target;
@AccessTimeout(0)
public @interface AwaitNever {
-}
-</code></pre>
-<h2>@AwaitForever</h2>
+}</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="__awaitforever">@AwaitForever</h3>
+<div class="paragraph">
<p>Just as <code>0</code> carries the special meaning of "never wait", a value of <code>-1</code> means "wait forever."</p>
-<p>As long as we're being picky, which we can be with meta-annotations, Technically "wait forever" is not the best description. The actual methods of the <code>javax.util.concurrent</code> APIs use "await" rather than "wait". One (wait) perphaps implies a command to wait, which this is not, and the other (await) perhaps better implies that waiting is possible but not a certainty. So we will use "await" in our annotation names.</p>
+</div>
+<div class="paragraph">
+<p>As long as we’re being picky, which we can be with meta-annotations,
+Technically "wait forever" is not the best description. The actual methods of the <code>javax.util.concurrent</code> APIs use "await" rather than "wait". One (wait) perphaps implies a
+command to wait, which this is not, and the other (await) perhaps better implies that waiting is possible but not a certainty. So we will use "await" in our annotation names.</p>
+</div>
+<div class="paragraph">
<p>We make our own <code>@AwaitForever</code> and annotate it with <code>@AccessTimeout(0)</code> and <code>@Metatype</code></p>
-<pre><code>package org.superbiz.accesstimeout.api;
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">package org.superbiz.accesstimeout.api;
import javax.ejb.AccessTimeout;
import java.lang.annotation.ElementType;
@@ -154,42 +217,101 @@ import java.lang.annotation.Target;
@AccessTimeout(-1)
public @interface AwaitForever {
-}
-</code></pre>
-<h2>@AwaitBriefly</h2>
-<p>Non <code>-1</code> and <code>0</code> values to <code>@AccessTimeout</code> actually involve the full breadth of the annotation. Here is where you get to specify the maximum number minutes, seconds, milliseconds, etc. where one might await access to the bean instance.</p>
-<pre><code>@Metatype
+}</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="__awaitbriefly">@AwaitBriefly</h3>
+<div class="paragraph">
+<p>Non <code>-1</code> and <code>0</code> values to <code>@AccessTimeout</code> actually involve the full breadth of the annotation. Here is where you get to specify the maximum number minutes, seconds,
+milliseconds, etc. where one might await access to the bean instance.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">@Metatype
@Retention(RetentionPolicy.RUNTIME)
@Target({ElementType.METHOD, ElementType.TYPE})
@AccessTimeout(value = 5, unit = TimeUnit.SECONDS)
public @interface AwaitBriefly {
-}
-</code></pre>
-<h1>Configuration vs Operation</h1>
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_configuration_vs_operation">Configuration vs Operation</h2>
+<div class="sectionbody">
+<div class="paragraph">
<p>Once you create a few meta-annotations and the fun becomes common-place, questoins start to raise in your mind on how to best get the benefits of meta-annotations.</p>
-<p>You have to really start thinking about how you want to approach your usage of meta-annotation and really put your designer hat on. The fundamental question is<br/><strong>configuration vs operation</strong> and the answer is subjective; how much flexibility do you want to design into your applications and where?</p>
-<h2>Configuration names <small>describing the configuration</small></h2>
-<p>The simplest approach is to name your meta-annotations after the <strong>configuration</strong> they encapsulate. We've been following that format so far with <code>@AwaitNever</code> and <code>@AwaitForever</code> to clearly reflect the contents of each meta-annotation (<code>@AccessTimeout(-1)</code> and <code>@AccessTimeout(0)</code> respectively).</p>
-<p>The <strong>cons</strong> of this approach is that should you want to change the configuration of the application by only changing the meta-annotations -- this is one of the potential benefits of meta-annotations -- but this may change the meaning of the annotation. Certainly, the <code>@AwaitNever</code> meta-annotation can have no other value than <code>0</code> if it is to live up to its name.</p>
-<h2>Operation names <small>describing the code</small></h2>
-<p>The alternate approach is to name your meta-annotations after the <strong>operations</strong> they apply to. In short, to describe the code itself and not the configuration. So, names like<br/><code>@OrderCheckTimeout</code> or <code>@TwitterUpdateTimeout</code>. These names are configuration-change-proof. They would not change if the configuration changes and in fact they can facilitate<br/>finder-grained control over the configuration of an application.</p>
-<p>The <strong>cons</strong> of this approach is that requires far more deliberation and consideration, not to mention more annotations. Your skills as an architect, designer and ability to think as a administrator will be challenged. You must be good at wearing your dev-opts hat.</p>
-<h2>Pragmatism <small>best of both worlds</small></h2>
-<p>Fortunately, meta-annotations are recursive. You can do a little of both.</p>
-<pre><code>@Metatype
+</div>
+<div class="paragraph">
+<p>You have to really start thinking about how you want to approach your usage of meta-annotation and really put your designer hat on. The fundamental question is
+<strong>configuration vs operation</strong> and the answer is subjective; how much flexibility do you want to design into your applications and where?</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_configuration_names_span_class_small_describing_the_configuration_span">Configuration names <span class="small">describing the configuration</span></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The simplest approach is to name your meta-annotations after the <strong>configuration</strong> they encapsulate. We’ve been following that format so far with <code>@AwaitNever</code> and <code>@AwaitForever</code>
+to clearly reflect the contents of each meta-annotation (<code>@AccessTimeout(-1)</code> and <code>@AccessTimeout(0)</code> respectively).</p>
+</div>
+<div class="paragraph">
+<p>The <strong>cons</strong> of this approach is that should you want to change the configuration of the application by only changing the meta-annotations — this is one of the potential benefits
+of meta-annotations — but this may change the meaning of the annotation. Certainly, the <code>@AwaitNever</code> meta-annotation can have no other value than <code>0</code> if it is to live up to its name.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_operation_names_span_class_small_describing_the_code_span">Operation names <span class="small">describing the code</span></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The alternate approach is to name your meta-annotations after the <strong>operations</strong> they apply to. In short, to describe the code itself and not the configuration. So, names like
+<code>@OrderCheckTimeout</code> or <code>@TwitterUpdateTimeout</code>. These names are configuration-change-proof. They would not change if the configuration changes and in fact they can facilitate
+finder-grained control over the configuration of an application.</p>
+</div>
+<div class="paragraph">
+<p>The <strong>cons</strong> of this approach is that requires far more deliberation and consideration, not to mention more annotations. Your skills as an architect, designer and ability to think as
+a administrator will be challenged. You must be good at wearing your dev-opts hat.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_pragmatism_span_class_small_best_of_both_worlds_span">Pragmatism <span class="small">best of both worlds</span></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Fortunately, meta-annotations are recursive. You can do a little of both.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">@Metatype
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.METHOD)
@AwaitBriefly
public @interface TwitterUpdateTimeout {
-}
-</code></pre>
-<p>Of course you still need to be very deliberate on how your annotations are used. When using a "configuration" named meta-annotation in code it can help to say to yourself,<br/>"I do not want to reconfigure this later." If that doesn't feel quite right, put the extra effort into creating an operation named annotation and use in that code.</p>
-<h1>Applying the Meta-Annotations</h1>
-<p>Putting it all together, here's how we might apply our meta-annotations to the <a href="../access-timeout/README.html">access-timeout</a> example.</p>
-<h2>Before</h2>
-<pre><code>package org.superbiz.accesstimeout;
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Of course you still need to be very deliberate on how your annotations are used. When using a "configuration" named meta-annotation in code it can help to say to yourself,
+"I do not want to reconfigure this later." If that doesn’t feel quite right, put the extra effort into creating an operation named annotation and use in that code.</p>
+</div>
+</div>
+</div>
+<h1 id="_applying_the_meta_annotations" class="sect0">Applying the Meta-Annotations</h1>
+<div class="paragraph">
+<p>Putting it all together, here’s how we might apply our meta-annotations to the [access-timeout](../access-timeout/README.html) example.</p>
+</div>
+<div class="sect2">
+<h3 id="_before">Before</h3>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">package org.superbiz.accesstimeout;
import javax.ejb.AccessTimeout;
import javax.ejb.Asynchronous;
@@ -202,8 +324,8 @@ import java.util.concurrent.TimeUnit;
import static javax.ejb.LockType.WRITE;
/**
- * @version $Revision$ $Date$
- */
+ * @version $Revision$ $Date$
+ */
@Singleton
@Lock(WRITE)
public class BusyBee {
@@ -236,10 +358,15 @@ public class BusyBee {
// do something
}
-}
-</code></pre>
-<h2>After</h2>
-<pre><code>package org.superbiz.accesstimeout;
+}</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_after">After</h3>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">package org.superbiz.accesstimeout;
import org.superbiz.accesstimeout.api.AwaitBriefly;
import org.superbiz.accesstimeout.api.AwaitForever;
@@ -254,8 +381,8 @@ import java.util.concurrent.Future;
import static javax.ejb.LockType.WRITE;
/**
- * @version $Revision$ $Date$
- */
+ * @version $Revision$ $Date$
+ */
@Singleton
@Lock(WRITE)
public class BusyBee {
@@ -288,8 +415,10 @@ public class BusyBee {
// do something
}
-}
-</code></pre>
+}</code></pre>
+</div>
+</div>
+</div>
</div>
</div>
Modified: tomee/site/trunk/content/tomee-8.0/examples/access-timeout.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/examples/access-timeout.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/examples/access-timeout.html (original)
+++ tomee/site/trunk/content/tomee-8.0/examples/access-timeout.html Tue Dec 25 04:38:58 2018
@@ -88,58 +88,147 @@
<div class="col-md-12">
<div class='page-header'>
- <h1>@AccessTimeout annotation</h1>
+ <h1>@AccessTimeout Annotation</h1>
</div>
</div>
</div>
<div class="row">
<div class="col-md-12">
- <p>Before taking a look at <code>@AccessTimeout</code>, it might help to see when a caller might have to "wait"</p>
-<h2>Waiting</h2>
-<h3>Stateful Bean</h3>
-<blockquote>
- <p>By default, clients are allowed to make concurrent calls to a stateful session object and the container is required to serialize such concurrent requests. Note that the container never permits multi-threaded access to the actual stateful session bean instance. For this reason, Read/Write method locking metadata, as well as the bean-managed concurrency mode, are not applicable to stateful session beans and must not be used.</p>
-</blockquote>
+ <div id="preamble">
+<div class="sectionbody">
+<div class="paragraph">
+<p>Before taking a look at <code>@AccessTimeout</code>, it might help to see when a caller might have to "wait"</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_waiting">Waiting</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="_stateful_bean">Stateful Bean</h3>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+By default, clients are allowed to make concurrent calls to a stateful session object and the container is required to serialize such concurrent requests. The container never permits multi-threaded access to the stateful session bean instance. For this reason, Read/Write method locking metadata, as well as the bean-managed concurrency mode, are not applicable to stateful session beans and must not be used.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
<p>This means that when a method <code>foo()</code> of a stateful bean instance is being executed and a second request comes in for that method or another method, EJB container would serialize the second request. It would not let the method be executed concurrently but wait until the first request is processed.</p>
+</div>
+<div class="paragraph">
<p>The client would wait also when <code>@Stateful</code> bean is in a transaction and the client is invoking it from outside that transaction.</p>
-<h3>Stateless Bean</h3>
-<p>Say there are 20 instances of a bean in the pool and all of them are busy. Now when the next request comes in, the processing <em>might wait</em> for a bean to be available in the pool. (Note: Pooling sematics, if any, are not covered by the spec. The vendor's pooling semantics might or might not involve a wait condition)</p>
-<h3>Singleton Bean</h3>
-<p>The container enforces a single-threaded access by default to singleton beans. That's the equivalent of annotating with <code>@Lock(Write)</code>. So when a <code>@Lock(Write)</code> method is executing, all other <code>@Lock(READ)</code> and <code>@Lock(WRITE)</code> method invocations would have to wait.</p>
-<h3>Summary</h3>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_stateless_bean">Stateless Bean</h3>
+<div class="paragraph">
+<p>If there are 20 instances of a bean in the pool and all of them are busy. When the next request comes in, the processing <strong>might wait</strong> for a bean to be available in the pool. (Note: Pooling sematics, if any, are not covered by the spec. The vendor’s pooling semantics might or might not involve a wait condition)</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_singleton_bean">Singleton Bean</h3>
+<div class="paragraph">
+<p>The container enforces a single-threaded access by default to singleton beans. That’s the equivalent of annotating with <code>@Lock(Write)</code>. So when a <code>@Lock(Write)</code> method is executing, all other <code>@Lock(READ)</code> and <code>@Lock(WRITE)</code> method invocations would have to wait.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_summary">Summary</h3>
+<div class="ulist">
<ul>
- <li><code>@Singleton</code> - an <code>@Lock(WRITE)</code> method is being invoked and container-managed concurrency is being used. All methods are <code>@Lock(WRITE)</code> by default.</li>
- <li><code>@Stateful</code> - any method of the instance is being invoked and a second invocation occurs. OR the <code>@Stateful</code> bean is in a transaction and the caller is invoking it from outside that transaction.</li>
- <li><code>@Stateless</code> - no instances are available in the pool. As noted, however, pooling sematics, if any, are not covered by the spec. If the vendor's pooling semantics do involve a wait condition, the @AccessTimeout should apply.</li>
+<li>
+<p><code>@Singleton</code> - an <code>@Lock(WRITE)</code> method is being invoked and container-managed concurrency is being used. All methods are <code>@Lock(WRITE)</code> by default.</p>
+</li>
+<li>
+<p><code>@Stateful</code> - any method of the instance is being invoked and a second invocation occurs. OR the <code>@Stateful</code> bean is in a transaction and the caller is invoking it from outside that transaction.</p>
+</li>
+<li>
+<p><code>@Stateless</code> - no instances are available in the pool. As noted, however, pooling sematics, if any, are not covered by the spec. If the vendor’s pooling semantics do involve a wait condition, the @AccessTimeout should apply.</p>
+</li>
</ul>
-<h1>@AccessTimeout</h1>
+</div>
+</div>
+</div>
+</div>
+<h1 id="__accesstimeout" class="sect0">@AccessTimeout</h1>
+<div class="paragraph">
<p>The <code>@AccessTimeout</code> is simply a convenience wrapper around the <code>long</code> and <code>TimeUnit</code> tuples commonly used in the <code>java.util.concurrent</code> API.</p>
-<pre><code>import java.util.concurrent.TimeUnit;
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">import java.util.concurrent.TimeUnit;
@Target({METHOD, TYPE})
@Retention(RUNTIME)
public @interface AccessTimeout {
long value();
TimeUnit unit() default TimeUnit.MILLISECONDS;
-}
-</code></pre>
-<h2>Usage</h2>
-<p>A method or class can be annotated with @AccessTimeout to specify the maximum time a call might wait for access to the bean should a wait condition occur.</p>
+}</code></pre>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_usage">Usage</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>A method or class can be annotated with <code>@AccessTimeout</code> to specify the maximum time a call might wait for access to the bean should a wait condition occur.</p>
+</div>
+<div class="paragraph">
<p>The semantics of the value element are as follows:</p>
+</div>
+<div class="ulist">
<ul>
- <li>A <code>value</code> > 0 indicates a timeout value in the units specified by the <code>unit</code> element.</li>
- <li>A <code>value</code> of 0 means concurrent access is not permitted.</li>
- <li>A <code>value</code> of -1 indicates that the client request will block indefinitely until forward progress can proceed.</li>
+<li>
+<p>A <code>value</code> > 0 indicates a timeout value in the units specified by the <code>unit</code> element.</p>
+</li>
+<li>
+<p>A <code>value</code> of 0 means concurrent access is not permitted.</p>
+</li>
+<li>
+<p>A <code>value</code> of -1 indicates that the client request will block indefinitely until forward progress can proceed.</p>
+</li>
</ul>
+</div>
+<div class="paragraph">
<p>Just as simple as that !</p>
-<h3>What exception would the client receive, with a timeout ?</h3>
-<p>Quoting from the spec, "if a client-invoked business method is in progress on an instance when another client-invoked call, from the same or different client, arrives at the same instance of a stateful session bean, if the second client is a client of the bean�s business interface or no-interface view, the concurrent invocation must result in the second client receiving a javax.ejb.ConcurrentAccessException[15]. If the EJB 2.1 client view is used, the container must throw a java.rmi.RemoteException if the second client is a remote client, or a javax.ejb.EJBException if the second client is a local client"</p>
-<h3>No standard default</h3>
-<p>Note that the <code>value</code> attribute has no default. This was intentional and intended to communicate that if <code>@AccessTimeout</code> is not explicitly used, the behavior you get is vendor-specific.</p>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+What exception would the client receive, with a timeout ?
+Quoting from the spec, "if a client-invoked business method is in progress on an instance when another client-invoked call, from the same or different client, arrives at the same instance of a stateful session bean, if the second client is a client of the bean’s business interface or no-interface view, the concurrent invocation must result in the second client receiving a javax.ejb.ConcurrentAccessException[15]. If the EJB 2.1 client view is used, the container must throw a java.rmi.RemoteException if the second client is a remote client, or a javax.ejb.EJBException if the second client is a local client"
+</td>
+</tr>
+</table>
+</div>
+<div class="sect2">
+<h3 id="_no_standard_default">No standard default</h3>
+<div class="paragraph">
+<p>Note that the <code>value</code> attribute has no default. This was intentional and intended to communicate that if <code>@AccessTimeout</code> is not explicitly used, the behavior you get is vendor-specific.</p>
+</div>
+<div class="paragraph">
<p>Some vendors will wait for a preconfigured time and throw <code>javax.ejb.ConcurrentAccessException</code>, some vendors will throw it immediately.</p>
-<h1>Example</h1>
-<p>Here we have a simple @Singleton bean that has three synchronous methods and one <code>@Asynchronous</code> method. The bean itself is annotated <code>@Lock(WRITE)</code> so that only one thread may access the <code>@Singleton</code> at a time. This is the default behavior of an <code>@Singleton</code> bean, so explicit usage of <code>@Lock(WRITE)</code> is not needed but is rather nice for clarity as the single-threaded nature of the bean is important to the example.</p>
-<pre><code>@Singleton
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_example">Example</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Here we have a simple @Singleton bean that has three synchronous methods and one <code>@Asynchronous</code> method. The bean itself is annotated <code>@Lock(WRITE)</code> so that only one thread may access the <code>@Singleton</code> at a time. This is the default behavior of an <code>@Singleton</code> bean, so explicit usage of <code>@Lock(WRITE)</code> is not needed but is rather nice for clarity as the single-threaded nature of the bean is important to the example.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">@Singleton
@Lock(WRITE)
public class BusyBee {
@@ -170,11 +259,15 @@ public class BusyBee {
public void justDoIt() {
// do something
}
-
-}
-</code></pre>
-<p>The <code>@Asynchronous</code> method is not a critical part of <code>@AccessTimeout</code>, but serves as a simple way to "lock" the bean for testing purposes. It allows us to easily test the concurrent behavior of the bean.</p>
-<pre><code>public class BusyBeeTest extends TestCase {
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The <code>@Asynchronous</code> method is not a critical part of <code>@AccessTimeout</code>, but serves as a simple way to "lock" the bean for testing purposes. It allows us to easily test the concurrent behavior of the bean.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">public class BusyBeeTest extends TestCase {
public void test() throws Exception {
@@ -182,7 +275,7 @@ public class BusyBee {
final CountDownLatch ready = new CountDownLatch(1);
- final BusyBee busyBee = (BusyBee) context.lookup("java:global/access-timeout/BusyBee");
+ final BusyBee busyBee = (BusyBee) context.lookup("java:global/access-timeout/BusyBee");
// This asynchronous method will never exit
busyBee.stayBusy(ready);
@@ -200,7 +293,7 @@ public class BusyBee {
try {
busyBee.doItNow();
- fail("The bee should be busy");
+ fail("The bee should be busy");
} catch (Exception e) {
// the bee is still too busy as expected
}
@@ -214,7 +307,7 @@ public class BusyBee {
try {
busyBee.doItSoon();
- fail("The bee should be busy");
+ fail("The bee should be busy");
} catch (Exception e) {
// the bee is still too busy as expected
}
@@ -229,18 +322,32 @@ public class BusyBee {
private long seconds(long start) {
return TimeUnit.NANOSECONDS.toSeconds(System.nanoTime() - start);
}
-}
-</code></pre>
-<h1>Running</h1>
-<pre><code>-------------------------------------------------------
- T E S T S
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_running">Running</h2>
+<div class="sectionbody">
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-bash" data-lang="bash">mvn clean test</code></pre>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_output">Output</h3>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-bash" data-lang="bash">-------------------------------------------------------
+ T E S T S
-------------------------------------------------------
Running org.superbiz.accesstimeout.BusyBeeTest
Apache OpenEJB 4.0.0-beta-1 build: 20111002-04:06
http://tomee.apache.org/
INFO - openejb.home = /Users/dblevins/examples/access-timeout
INFO - openejb.base = /Users/dblevins/examples/access-timeout
-INFO - Using 'javax.ejb.embeddable.EJBContainer=true'
+INFO - Using 'javax.ejb.embeddable.EJBContainer=true'
INFO - Configuring Service(id=Default Security Service, type=SecurityService, provider-id=Default Security Service)
INFO - Configuring Service(id=Default Transaction Manager, type=TransactionManager, provider-id=Default Transaction Manager)
INFO - Found EjbModule in classpath: /Users/dblevins/examples/access-timeout/target/classes
@@ -250,12 +357,12 @@ INFO - Configuring Service(id=Default Si
INFO - Auto-creating a container for bean BusyBee: Container(type=SINGLETON, id=Default Singleton Container)
INFO - Configuring Service(id=Default Managed Container, type=Container, provider-id=Default Managed Container)
INFO - Auto-creating a container for bean org.superbiz.accesstimeout.BusyBeeTest: Container(type=MANAGED, id=Default Managed Container)
-INFO - Enterprise application "/Users/dblevins/examples/access-timeout" loaded.
+INFO - Enterprise application "/Users/dblevins/examples/access-timeout" loaded.
INFO - Assembling app: /Users/dblevins/examples/access-timeout
-INFO - Jndi(name="java:global/access-timeout/BusyBee!org.superbiz.accesstimeout.BusyBee")
-INFO - Jndi(name="java:global/access-timeout/BusyBee")
-INFO - Jndi(name="java:global/EjbModule748454644/org.superbiz.accesstimeout.BusyBeeTest!org.superbiz.accesstimeout.BusyBeeTest")
-INFO - Jndi(name="java:global/EjbModule748454644/org.superbiz.accesstimeout.BusyBeeTest")
+INFO - Jndi(name="java:global/access-timeout/BusyBee!org.superbiz.accesstimeout.BusyBee")
+INFO - Jndi(name="java:global/access-timeout/BusyBee")
+INFO - Jndi(name="java:global/EjbModule748454644/org.superbiz.accesstimeout.BusyBeeTest!org.superbiz.accesstimeout.BusyBeeTest")
+INFO - Jndi(name="java:global/EjbModule748454644/org.superbiz.accesstimeout.BusyBeeTest")
INFO - Created Ejb(deployment-id=org.superbiz.accesstimeout.BusyBeeTest, ejb-name=org.superbiz.accesstimeout.BusyBeeTest, container=Default Managed Container)
INFO - Created Ejb(deployment-id=BusyBee, ejb-name=BusyBee, container=Default Singleton Container)
INFO - Started Ejb(deployment-id=org.superbiz.accesstimeout.BusyBeeTest, ejb-name=org.superbiz.accesstimeout.BusyBeeTest, container=Default Managed Container)
@@ -265,8 +372,12 @@ Tests run: 1, Failures: 0, Errors: 0, Sk
Results :
-Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
-</code></pre>
+Tests run: 1, Failures: 0, Errors: 0, Skipped: 0</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
</div>
</div>
Modified: tomee/site/trunk/content/tomee-8.0/examples/index.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/examples/index.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/examples/index.html (original)
+++ tomee/site/trunk/content/tomee-8.0/examples/index.html Tue Dec 25 04:38:58 2018
@@ -93,20 +93,6 @@
</div>
<div class="row">
<div class="col-md-4">
- <div class="group-title">Misc</div>
- <ul class="group">
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="applet.html">Applet</a></li>
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="ejb-examples.html">EJB Examples</a></li>
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="ejb-webservice.html">EJB Webservice</a></li>
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="helloworld-weblogic.html">Helloworld Weblogic</a></li>
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="jsf-managedBean-and-ejb.html">JSF Application that uses managed-bean and ejb</a></li>
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="jsf-cdi-and-ejb.html">JSF-CDI-EJB</a></li>
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="moviefun.html">Movies Complete</a></li>
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="mvc-cxf.html">MVC-CXF</a></li>
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="polling-parent.html">polling-parent</a></li>
- </ul>
- </div>
- <div class="col-md-4">
<div class="group-title">CDI</div>
<ul class="group">
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="cdi-application-scope.html">CDI @ApplicationScoped</a></li>
@@ -130,12 +116,10 @@
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="webservice-ws-security.html">Webservice Ws Security</a></li>
</ul>
</div>
- </div>
- <div class="row">
<div class="col-md-4">
<div class="group-title">EJB</div>
<ul class="group">
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="access-timeout.html">@AccessTimeout annotation</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="access-timeout.html">@AccessTimeout Annotation</a></li>
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="async-postconstruct.html">@Asynchronous @PostConstruct</a></li>
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="async-methods.html">@Asynchronous Methods</a></li>
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="interceptors.html">Interceptors</a></li>
@@ -143,6 +127,28 @@
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="schedule-methods.html">Schedule Methods</a></li>
</ul>
</div>
+ </div>
+ <div class="row">
+ <div class="col-md-4">
+ <div class="group-title">REST</div>
+ <ul class="group">
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="moviefun-rest.html">MovieFun REST</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="rest-example.html">REST Example</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="rest-example-with-application.html">REST Example with Application</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="rest-on-ejb.html">REST on EJB</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="simple-rest.html">Simple REST</a></li>
+ </ul>
+ </div>
+ <div class="col-md-4">
+ <div class="group-title">Unknown</div>
+ <ul class="group">
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="java-modules.html">Java modules example with a simple REST resource</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="mp-custom-healthcheck.html">MicroProfile Custom Health Check</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="mp-faulttolerance-fallback.html">Microprofile Fault Tolerance - Fallback</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="mp-opentracing-traced.html">mp-opentracing-traced</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="mp-rest-client.html">mp-rest-client</a></li>
+ </ul>
+ </div>
<div class="col-md-4">
<div class="group-title">Meta-Annotations</div>
<ul class="group">
@@ -153,6 +159,8 @@
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="testing-security-meta.html">Testing Security Meta</a></li>
</ul>
</div>
+ </div>
+ <div class="row">
<div class="col-md-4">
<div class="group-title">Session Beans</div>
<ul class="group">
@@ -162,8 +170,6 @@
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="simple-stateless-with-descriptor.html">Simple Stateless with Descriptor</a></li>
</ul>
</div>
- </div>
- <div class="row">
<div class="col-md-4">
<div class="group-title">Testing Techniques</div>
<ul class="group">
@@ -174,15 +180,6 @@
</ul>
</div>
<div class="col-md-4">
- <div class="group-title">REST</div>
- <ul class="group">
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="rest-example.html">REST Example</a></li>
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="rest-example-with-application.html">REST Example with Application</a></li>
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="rest-on-ejb.html">REST on EJB</a></li>
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="simple-rest.html">Simple REST</a></li>
- </ul>
- </div>
- <div class="col-md-4">
<div class="group-title">DataSources</div>
<ul class="group">
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="datasource-ciphered-password.html">DataSource Ciphered Password</a></li>
@@ -264,21 +261,14 @@
</ul>
</div>
<div class="col-md-4">
- <div class="group-title">Unknown</div>
- <ul class="group">
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="java-modules.html">Java modules example with a simple REST resource</a></li>
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="mp-faulttolerance-retry.html">mp-faulttolerance-retry</a></li>
- </ul>
- </div>
- </div>
- <div class="row">
- <div class="col-md-4">
<div class="group-title">Environment Entries</div>
<ul class="group">
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="custom-injection.html">Custom Injection</a></li>
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="injection-of-env-entry.html">Using EnvEntries</a></li>
</ul>
</div>
+ </div>
+ <div class="row">
<div class="col-md-4">
<div class="group-title">EJB Legacy</div>
<ul class="group">
@@ -287,6 +277,12 @@
</ul>
</div>
<div class="col-md-4">
+ <div class="group-title">Histogram</div>
+ <ul class="group">
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="mp-metrics-histogram.html">mp-metrics-histogram</a></li>
+ </ul>
+ </div>
+ <div class="col-md-4">
<div class="group-title">Java EE Connectors</div>
<ul class="group">
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="quartz-app.html">Quartz Resource Adapter usage</a></li>
@@ -295,6 +291,35 @@
</div>
<div class="row">
<div class="col-md-12">
+ <div class="group-title large">Misc</div>
+ </div>
+ </div>
+ <div class="row">
+ <div class="col-md-4">
+ <ul class="group">
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="applet.html">Applet</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="ejb-examples.html">EJB Examples</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="ejb-webservice.html">EJB Webservice</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="helloworld-weblogic.html">Helloworld Weblogic</a></li>
+ </ul>
+ </div>
+ <div class="col-md-4">
+ <ul class="group">
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="jsf-managedBean-and-ejb.html">JSF Application that uses managed-bean and ejb</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="jsf-cdi-and-ejb.html">JSF-CDI-EJB</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="moviefun.html">Movies Complete</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="mvc-cxf.html">MVC-CXF</a></li>
+ </ul>
+ </div>
+ <div class="col-md-4">
+ <ul class="group">
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="mvc-resteasy.html">MVC-RestEasy</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="polling-parent.html">polling-parent</a></li>
+ </ul>
+ </div>
+ </div>
+ <div class="row">
+ <div class="col-md-12">
<div class="group-title large">Unrevised</div>
</div>
</div>
@@ -316,19 +341,21 @@
<div class="col-md-4">
<ul class="group">
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="javamail.html">Javamail API</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="mp-config-example.html">Microprofile Config</a></li>
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="connector-war.html">Movies Complete</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="mp-faulttolerance-retry.html">mp-faulttolerance-retry</a></li>
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="mp-metrics-counted.html">mp-metrics-counted</a></li>
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="mp-metrics-timed.html">mp-metrics-timed</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="mp-rest-jwt.html">mp-rest-jwt</a></li>
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="mtom.html">mtom</a></li>
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="myfaces-codi-demo.html">MyFaces CODI Demo</a></li>
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="persistence-fragment.html">Persistence Fragment</a></li>
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="reload-persistence-unit-properties.html">Reload Persistence Unit Properties</a></li>
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="rest-mp-jwt.html">rest-mp-jwt</a></li>
- <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="schedule-events.html">Schedule CDI Events</a></li>
</ul>
</div>
<div class="col-md-4">
<ul class="group">
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="reload-persistence-unit-properties.html">Reload Persistence Unit Properties</a></li>
+ <li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="schedule-events.html">Schedule CDI Events</a></li>
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="simple-mdb-and-cdi.html">Simple MDB and CDI</a></li>
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="rest-xml-json.html">Simple REST</a></li>
<li class="group-item"><span class="group-item-i" ><i class="fa fa-angle-right"></i></span><a href="rest-cdi.html">Simple REST with CDI</a></li>
Modified: tomee/site/trunk/content/tomee-8.0/examples/jpa-hibernate.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-8.0/examples/jpa-hibernate.html?rev=1849711&r1=1849710&r2=1849711&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-8.0/examples/jpa-hibernate.html (original)
+++ tomee/site/trunk/content/tomee-8.0/examples/jpa-hibernate.html Tue Dec 25 04:38:58 2018
@@ -95,8 +95,9 @@
<div class="row">
<div class="col-md-12">
- <p><em>Help us document this example! Click the blue pencil icon in the upper right to edit this page.</em></p>
+ <p>This example shows the persist, remove and creation a query in JPA Hibernate. The Java Persistence API (JPA) is a Java specification for accessing, persisting, and managing data between Java objects / classes and a relational database.</p>
<h2>Movie</h2>
+<p>Define the class Movie as an entity with de annotation @Entity</p>
<pre><code>package org.superbiz.injection.h3jpa;
import javax.persistence.Entity;
@@ -151,6 +152,7 @@ public class Movie {
}
</code></pre>
<h2>Movies</h2>
+<p>@PersistenceContext A persistence context is a set of entities such that for any persistent identity there is a unique entity instance.<br/>@EntityManager is associated with a persistence context. Is at the core of JPA, supported by some methods: persist, remove,merge, find,</p>
<pre><code>package org.superbiz.injection.h3jpa;
import javax.ejb.Stateful;
@@ -236,6 +238,9 @@ public class MoviesTest extends TestCase
}
</code></pre>
<h1>Running</h1>
+<p>To run the example via maven:</p>
+<p>cd jpa-hibernate mvn clean install</p>
+<p>Which will generate output similar to the following:</p>
<pre><code>-------------------------------------------------------
T E S T S
-------------------------------------------------------