This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/tomee-site-pub.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 7c53ff7 [site-publish] source tomee-site-generator
https://github.com/apache/tomee-site-generator
https://ci-builds.apache.org/job/Tomee/job/site-publish
7c53ff7 is described below
commit 7c53ff759f174ce0f77209e48de1354d468d46ff
Author: jenkins <[email protected]>
AuthorDate: Tue Nov 9 00:46:01 2021 +0000
[site-publish] source tomee-site-generator
https://github.com/apache/tomee-site-generator
https://ci-builds.apache.org/job/Tomee/job/site-publish
---
.../concurrent/ManagedExecutorDefinition.html | 7 +++++++
.../ManagedScheduledExecutorDefinition.html | 7 +++++++
.../concurrent/ManagedThreadFactoryDefinition.html | 24 +++++++++++++++-------
.../jakarta/servlet/jsp/SkipPageException.html | 2 +-
4 files changed, 32 insertions(+), 8 deletions(-)
diff --git
a/jakartaee-9.0/javadoc/jakarta/enterprise/concurrent/ManagedExecutorDefinition.html
b/jakartaee-9.0/javadoc/jakarta/enterprise/concurrent/ManagedExecutorDefinition.html
index 74b74c8..155a3a8 100644
---
a/jakartaee-9.0/javadoc/jakarta/enterprise/concurrent/ManagedExecutorDefinition.html
+++
b/jakartaee-9.0/javadoc/jakarta/enterprise/concurrent/ManagedExecutorDefinition.html
@@ -271,6 +271,13 @@ public @interface <span
class="memberNameLabel">ManagedExecutorDefinition</span>
or the JNDI name of the Jakarta EE default <code>ContextService</code>
instance, <code>java:comp/DefaultContextService</code>.
<p>
+ The name of the <code>ContextService</code> must be no more granular
+ than the name of this <code>ManagedExecutorDefinition</code>. For example,
+ if this <code>ManagedExecutorDefinition</code> has a name in
<code>java:app</code>,
+ the <code>ContextService</code> can be in <code>java:app</code> or
<code>java:global</code>,
+ but not in <code>java:module</code> which would be ambiguous as to which
+ module's <code>ContextService</code> definition should be used.
+ <p>
The default value, <code>java:comp/DefaultContextService</code>, is the
JNDI name of the Jakarta EE default <code>ContextService</code>.</div>
<dl>
diff --git
a/jakartaee-9.0/javadoc/jakarta/enterprise/concurrent/ManagedScheduledExecutorDefinition.html
b/jakartaee-9.0/javadoc/jakarta/enterprise/concurrent/ManagedScheduledExecutorDefinition.html
index 703c2fe..b06ef7f 100644
---
a/jakartaee-9.0/javadoc/jakarta/enterprise/concurrent/ManagedScheduledExecutorDefinition.html
+++
b/jakartaee-9.0/javadoc/jakarta/enterprise/concurrent/ManagedScheduledExecutorDefinition.html
@@ -271,6 +271,13 @@ public @interface <span
class="memberNameLabel">ManagedScheduledExecutorDefiniti
or the JNDI name of the Jakarta EE default <code>ContextService</code>
instance, <code>java:comp/DefaultContextService</code>.
<p>
+ The name of the <code>ContextService</code> must be no more granular
+ than the name of this <code>ManagedScheduledExecutorDefinition</code>. For
example,
+ if this <code>ManagedScheduledExecutorDefinition</code> has a name in
<code>java:app</code>,
+ the <code>ContextService</code> can be in <code>java:app</code> or
<code>java:global</code>,
+ but not in <code>java:module</code> which would be ambiguous as to which
+ module's <code>ContextService</code> definition should be used.
+ <p>
The default value, <code>java:comp/DefaultContextService</code>, is the
JNDI name of the Jakarta EE default <code>ContextService</code>.</div>
<dl>
diff --git
a/jakartaee-9.0/javadoc/jakarta/enterprise/concurrent/ManagedThreadFactoryDefinition.html
b/jakartaee-9.0/javadoc/jakarta/enterprise/concurrent/ManagedThreadFactoryDefinition.html
index 44adb8a..832558b 100644
---
a/jakartaee-9.0/javadoc/jakarta/enterprise/concurrent/ManagedThreadFactoryDefinition.html
+++
b/jakartaee-9.0/javadoc/jakarta/enterprise/concurrent/ManagedThreadFactoryDefinition.html
@@ -251,13 +251,23 @@ public @interface <span
class="memberNameLabel">ManagedThreadFactoryDefinition</
<li class="blockList">
<h4>context</h4>
<pre>public abstract java.lang.String context</pre>
-<div class="block"><p>Determines how context is applied to threads from this
- thread factory.</p>
-
- <p>The default value indicates to use the default instance of
- <a href="../../../jakarta/enterprise/concurrent/ContextService.html"
title="interface in
jakarta.enterprise.concurrent"><code>ContextService</code></a> by specifying a
- <a
href="../../../jakarta/enterprise/concurrent/ContextServiceDefinition.html"
title="annotation in
jakarta.enterprise.concurrent"><code>ContextServiceDefinition</code></a> with
the name
- <code>java:comp/DefaultContextService</code>.</p></div>
+<div class="block">Determines how context is applied to threads from this
+ thread factory.
+ <p>
+ The name can be the name of a <a
href="../../../jakarta/enterprise/concurrent/ContextServiceDefinition.html"
title="annotation in
jakarta.enterprise.concurrent"><code>ContextServiceDefinition</code></a> or
+ the name of a <code>context-service</code> deployment descriptor element
+ or the JNDI name of the Jakarta EE default <code>ContextService</code>
+ instance, <code>java:comp/DefaultContextService</code>.
+ <p>
+ The name of the <code>ContextService</code> must be no more granular
+ than the name of this <code>ManagedThreadFactoryDefinition</code>. For
example,
+ if this <code>ManagedThreadFactoryDefinition</code> has a name in
<code>java:app</code>,
+ the <code>ContextService</code> can be in <code>java:app</code> or
<code>java:global</code>,
+ but not in <code>java:module</code> which would be ambiguous as to which
+ module's <code>ContextService</code> definition should be used.
+ <p>
+ The default value, <code>java:comp/DefaultContextService</code>, is the
+ JNDI name of the Jakarta EE default <code>ContextService</code>.</div>
<dl>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>instructions for capturing and propagating or clearing context.</dd>
diff --git a/jakartaee-9.0/javadoc/jakarta/servlet/jsp/SkipPageException.html
b/jakartaee-9.0/javadoc/jakarta/servlet/jsp/SkipPageException.html
index f62046c..3f87bfa 100644
--- a/jakartaee-9.0/javadoc/jakarta/servlet/jsp/SkipPageException.html
+++ b/jakartaee-9.0/javadoc/jakarta/servlet/jsp/SkipPageException.html
@@ -124,7 +124,7 @@
<pre>public class <span class="typeNameLabel">SkipPageException</span>
extends <a href="../../../jakarta/servlet/jsp/JspException.html" title="class
in jakarta.servlet.jsp">JspException</a></pre>
<div class="block">Exception to indicate the calling page must cease
evaluation. Thrown by a simple tag handler to indicate that the
- remainder of the page must not be evaluated. The result is propagated back to
the pagein the case where one tag
+ remainder of the page must not be evaluated. The result is propagated back to
the page in the case where one tag
invokes another (as can be the case with tag files). The effect is similar to
that of a Classic Tag Handler returning
Tag.SKIP_PAGE from doEndTag(). Jsp Fragments may also throw this exception.
This exception should not be thrown
manually in a JSP page or tag file - the behavior is undefined. The exception
is intended to be thrown inside
