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/artemis-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 22b1f86 Automatic Site Publish by Buildbot
22b1f86 is described below
commit 22b1f86c65fe9d84ce936e99d6b65250d2bf98a7
Author: buildbot <[email protected]>
AuthorDate: Mon Dec 22 11:57:37 2025 +0000
Automatic Site Publish by Buildbot
---
output/.htaccess | 1 +
.../artemis/documentation/latest/architecture.html | 26 +++++++++++-----------
...edding-activemq.html => embedding-artemis.html} | 20 ++++++++---------
.../artemis/documentation/latest/index.html | 2 +-
4 files changed, 25 insertions(+), 24 deletions(-)
diff --git a/output/.htaccess b/output/.htaccess
index f7ea330..c9c67a5 100644
--- a/output/.htaccess
+++ b/output/.htaccess
@@ -1,6 +1,7 @@
RewriteEngine On
RewriteCond %{HTTPS} !=on [NC]
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [R,L]
+RewriteRule
^components/artemis/documentation/latest/embedding-activemq.html(.*)$
https://%{SERVER_NAME}/components/artemis/documentation/latest/embedding-artemis.html$1
[R=301,L]
RewriteRule ^components/artemis/documentation/2.32.0(/?.*)$
https://%{SERVER_NAME}/components/artemis/documentation/previous/2.32.0$1
[R=301,L]
RewriteRule ^components/artemis/documentation/2.33.0(/?.*)$
https://%{SERVER_NAME}/components/artemis/documentation/previous/2.33.0$1
[R=301,L]
RewriteRule ^components/artemis/documentation/2.34.0(/?.*)$
https://%{SERVER_NAME}/components/artemis/documentation/previous/2.34.0$1
[R=301,L]
diff --git a/output/components/artemis/documentation/latest/architecture.html
b/output/components/artemis/documentation/latest/architecture.html
index 5db4b13..574897e 100644
--- a/output/components/artemis/documentation/latest/architecture.html
+++ b/output/components/artemis/documentation/latest/architecture.html
@@ -45,17 +45,17 @@
<div id="preamble">
<div class="sectionbody">
<div class="paragraph">
-<p>Apache ActiveMQ Artemis core is designed simply as set of Plain Old Java
Objects (POJOs) - we hope you like its clean-cut design.</p>
+<p>Apache Artemis core is designed simply as set of Plain Old Java Objects
(POJOs) - we hope you like its clean-cut design.</p>
</div>
<div class="paragraph">
-<p>Each Apache ActiveMQ Artemis server has its own ultra high performance
persistent journal, which it uses for message and other persistence.</p>
+<p>Each Apache Artemis server has its own ultra high performance persistent
journal, which it uses for message and other persistence.</p>
</div>
<div class="paragraph">
<p>Using a high performance journal allows outrageous persistence message
performance, something not achievable when using a relational database for
persistence (although JDBC is still an option if necessary).</p>
</div>
<div class="paragraph">
-<p>Apache ActiveMQ Artemis clients, potentially on different physical
machines, interact with the Apache ActiveMQ Artemis broker.
-Apache ActiveMQ Artemis currently ships three API implementations for
messaging at the client side:</p>
+<p>Apache Artemis clients, potentially on different physical machines,
interact with the Apache Artemis broker.
+Apache Artemis currently ships three API implementations for messaging at the
client side:</p>
</div>
<div class="olist arabic">
<ol class="arabic">
@@ -79,7 +79,7 @@ This difference was introduced due to the move from
Oracle’s Java EE to Ec
</ol>
</div>
<div class="paragraph">
-<p>Apache ActiveMQ Artemis also provides different protocol implementations on
the server so you can use respective clients for these protocols:</p>
+<p>Apache Artemis also provides different protocol implementations on the
server so you can use respective clients for these protocols:</p>
</div>
<div class="ulist">
<ul>
@@ -107,10 +107,10 @@ This difference was introduced due to the move from
Oracle’s Java EE to Ec
<p>JMS semantics are implemented by a JMS facade layer on the client side.</p>
</div>
<div class="paragraph">
-<p>The Apache ActiveMQ Artemis broker does not speak JMS and in fact does not
know anything about JMS, it is a protocol agnostic messaging server designed to
be used with multiple different protocols.</p>
+<p>The Apache Artemis broker does not speak JMS and in fact does not know
anything about JMS, it is a protocol agnostic messaging server designed to be
used with multiple different protocols.</p>
</div>
<div class="paragraph">
-<p>When a user uses the JMS API on the client side, all JMS interactions are
translated into operations on the Apache ActiveMQ Artemis core client API
before being transferred over the wire using the core protocol.</p>
+<p>When a user uses the JMS API on the client side, all JMS interactions are
translated into operations on the Apache Artemis core client API before being
transferred over the wire using the core protocol.</p>
</div>
<div class="paragraph">
<p>The broker always just deals with core API interactions.</p>
@@ -135,10 +135,10 @@ This difference was introduced due to the move from
Oracle’s Java EE to Ec
<h2 id="embedded-broker"><a class="anchor" href="#embedded-broker"></a><a
class="link" href="#embedded-broker">2. Embedded Broker</a></h2>
<div class="sectionbody">
<div class="paragraph">
-<p>Apache ActiveMQ Artemis core is designed as a set of simple POJOs so if you
have an application that requires messaging functionality internally but you
don’t want to expose that as an Apache ActiveMQ Artemis broker you can
directly instantiate and embed brokers in your own application.</p>
+<p>Apache Artemis core is designed as a set of simple POJOs so if you have an
application that requires messaging functionality internally but you
don’t want to expose that as an Apache Artemis broker you can directly
instantiate and embed brokers in your own application.</p>
</div>
<div class="paragraph">
-<p>Read more about <a
href="embedding-activemq.html#embedding-apache-activemq-artemis">embedding
Apache ActiveMQ Artemis</a>.</p>
+<p>Read more about <a href="embedding-artemis.html">embedding Apache
Artemis</a>.</p>
</div>
</div>
</div>
@@ -146,7 +146,7 @@ This difference was introduced due to the move from
Oracle’s Java EE to Ec
<h2 id="integrated-with-a-javajakarta-ee-application-server"><a class="anchor"
href="#integrated-with-a-javajakarta-ee-application-server"></a><a class="link"
href="#integrated-with-a-javajakarta-ee-application-server">3. Integrated with
a Java/Jakarta EE application server</a></h2>
<div class="sectionbody">
<div class="paragraph">
-<p>Apache ActiveMQ Artemis provides its own fully functional Java Connector
Architecture (JCA) adaptor which enables it to be integrated easily into any
Java/Jakarta EE (henceforth just "EE") compliant application server or servlet
engine.</p>
+<p>Apache Artemis provides its own fully functional Java Connector
Architecture (JCA) adaptor which enables it to be integrated easily into any
Java/Jakarta EE (henceforth just "EE") compliant application server or servlet
engine.</p>
</div>
<div class="paragraph">
<p>EE application servers provide Message Driven Beans (MDBs), which are a
special type of Enterprise Java Beans (EJBs) that can process messages from
sources such as JMS systems or mail systems.</p>
@@ -169,14 +169,14 @@ In fact, communicating with a JMS messaging system
directly, without using JCA w
It is possible to talk to a JMS messaging system directly from an EJB, MDB or
servlet without going through a JCA adapter, but this is not recommended since
you will not be able to take advantage of the JCA features, such as caching of
JMS sessions, which can result in poor performance.</p>
</div>
<div class="paragraph">
-<p>Note that all communication between EJB sessions or entity beans and
Message Driven beans go through the adaptor and not directly to Apache ActiveMQ
Artemis.</p>
+<p>Note that all communication between EJB sessions or entity beans and
Message Driven beans go through the adaptor and not directly to Apache
Artemis.</p>
</div>
<div class="paragraph">
-<p>The large arrow with the prohibited sign shows an EJB session bean talking
directly to the Apache ActiveMQ Artemis server.
+<p>The large arrow with the prohibited sign shows an EJB session bean talking
directly to the Apache Artemis server.
This is not recommended as you’ll most likely end up creating a new
connection and session every time you want to interact from the EJB, which is
an anti-pattern.</p>
</div>
</div>
</div>
</div>
</body>
-</html>
\ No newline at end of file
+</html>
diff --git
a/output/components/artemis/documentation/latest/embedding-activemq.html
b/output/components/artemis/documentation/latest/embedding-artemis.html
similarity index 92%
rename from
output/components/artemis/documentation/latest/embedding-activemq.html
rename to output/components/artemis/documentation/latest/embedding-artemis.html
index 47c7f9b..4489496 100644
--- a/output/components/artemis/documentation/latest/embedding-activemq.html
+++ b/output/components/artemis/documentation/latest/embedding-artemis.html
@@ -6,7 +6,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="generator" content="Asciidoctor 2.0.23">
<link rel="icon" type="image/png" href="images/favicon.png">
-<title>Embedding Apache ActiveMQ Artemis</title>
+<title>Embedding Apache Artemis</title>
<link rel="stylesheet" href="css/asciidoctor.css">
<link rel="stylesheet" href="css/font-awesome.css">
<link rel="stylesheet" href="css/rouge-github.css">
@@ -32,7 +32,7 @@
</head>
<body class="book toc2 toc-left">
<div id="header">
-<h1>Embedding Apache ActiveMQ Artemis</h1>
+<h1>Embedding Apache Artemis</h1>
<div id="toc" class="toc2">
<div id="toctitle"><a href="index.html">User Manual for 2.44.0</a></div>
<ul class="sectlevel1">
@@ -45,16 +45,16 @@
<div id="preamble">
<div class="sectionbody">
<div class="paragraph">
-<p>Apache ActiveMQ Artemis is designed as set of simple Plain Old Java Objects
(POJOs).
-This means Apache ActiveMQ Artemis can be instantiated and run in any
dependency injection framework such as Spring or Google Guice.
-It also means that if you have an application that could use messaging
functionality internally then it can <em>directly instantiate</em> Apache
ActiveMQ Artemis clients and servers in its own application code to perform
that functionality.
-We call this <em>embedding</em> Apache ActiveMQ Artemis.</p>
+<p>Apache Artemis is designed as set of simple Plain Old Java Objects (POJOs).
+This means Apache Artemis can be instantiated and run in any dependency
injection framework such as Spring or Google Guice.
+It also means that if you have an application that could use messaging
functionality internally then it can <em>directly instantiate</em> Apache
Artemis clients and servers in its own application code to perform that
functionality.
+We call this <em>embedding</em> Apache Artemis.</p>
</div>
<div class="paragraph">
<p>Examples of applications that might want to do this include any application
that needs very high performance, transactional, persistent messaging but
doesn’t want the hassle of writing it all from scratch.</p>
</div>
<div class="paragraph">
-<p>Embedding Apache ActiveMQ Artemis can be done in very few easy steps -
supply a <code>broker.xml</code> on the classpath or instantiate the
configuration object, instantiate the server, start it, and you have a Apache
ActiveMQ Artemis running in your JVM.
+<p>Embedding Apache Artemis can be done in very few easy steps - supply a
<code>broker.xml</code> on the classpath or instantiate the configuration
object, instantiate the server, start it, and you have a Apache Artemis running
in your JVM.
It’s as simple and easy as that.</p>
</div>
</div>
@@ -63,7 +63,7 @@ It’s as simple and easy as that.</p>
<h2 id="embedding-with-xml-configuration"><a class="anchor"
href="#embedding-with-xml-configuration"></a><a class="link"
href="#embedding-with-xml-configuration">1. Embedding with XML
configuration</a></h2>
<div class="sectionbody">
<div class="paragraph">
-<p>The simplest way to embed Apache ActiveMQ Artemis is to use the embedded
wrapper class and configure Apache ActiveMQ Artemis through
<code>broker.xml</code>.</p>
+<p>The simplest way to embed Apache Artemis is to use the embedded wrapper
class and configure Apache Artemis through <code>broker.xml</code>.</p>
</div>
<div class="paragraph">
<p>Here’s a simple example <code>broker.xml</code>:</p>
@@ -125,7 +125,7 @@ See the javadocs for this class for more details.</p>
</div>
<div class="paragraph">
<p>Create the <code>Configuration</code> object.
-This contains configuration information for an Apache ActiveMQ Artemis
instance.
+This contains configuration information for an Apache Artemis instance.
The setter methods of this class allow you to programmatically set
configuration options as described in the <a
href="configuration-index.html#configuration-reference">Server
Configuration</a> section.</p>
</div>
<div class="paragraph">
@@ -174,4 +174,4 @@ Just add the acceptor URL the same way you would through
the main configuration
</div>
</div>
</body>
-</html>
\ No newline at end of file
+</html>
diff --git a/output/components/artemis/documentation/latest/index.html
b/output/components/artemis/documentation/latest/index.html
index 6b2f308..41ea843 100644
--- a/output/components/artemis/documentation/latest/index.html
+++ b/output/components/artemis/documentation/latest/index.html
@@ -473,7 +473,7 @@
<p><a href="logging.html#logging">Logging</a></p>
</li>
<li>
-<p><a
href="embedding-activemq.html#embedding-apache-activemq-artemis">Embedding
Apache Artemis</a></p>
+<p><a href="embedding-artemis.html">Embedding Apache Artemis</a></p>
</li>
<li>
<p><a href="karaf.html#artemis-on-apache-karaf">Apache Karaf
Integration</a></p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
