(activemq-website) branch asf-site updated: Automatic Site Publish by Buildbot

[gi...@apache.org]

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/activemq-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new fb722e5bd Automatic Site Publish by Buildbot
fb722e5bd is described below

commit fb722e5bd5a472eb939bba9e09f27ec65feb3f9c
Author: buildbot <us...@infra.apache.org>
AuthorDate: Mon Sep 2 12:53:05 2024 +0000

    Automatic Site Publish by Buildbot
---
 .../classic/documentation/code-overview.html       | 24 +++++++++++-----------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/output/components/classic/documentation/code-overview.html b/output/components/classic/documentation/code-overview.html
index 20dc84d7f..0882a334c 100644
--- a/output/components/classic/documentation/code-overview.html
+++ b/output/components/classic/documentation/code-overview.html
@@ -102,13 +102,13 @@
 
 <h2 id="jms-client">JMS Client</h2>
 
-<p>The <a href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/package-summary.html">org.apache.activemq</a> package defines the core JMS client.</p>
+<p>The <a href="https://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/package-summary.html">org.apache.activemq</a> package defines the core JMS client.</p>
 
 <h2 id="transport">Transport</h2>
 
-<p>The JMS client and the message broker use the <a href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/transport/Transport.html">Transport</a> abstraction for sending around command objects (like a distributed <em>Command Pattern</em>). A TransportChannel typically deals with some kind of networking mechanism (TCP sockets using BIO, using NIO, UDP / multicast, SSL over sockets, JXTA, EmberIO etc). See the <a href="http://incubator.apache.org/active [...]
+<p>The JMS client and the message broker use the <a href="https://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/transport/Transport.html">Transport</a> abstraction for sending around command objects (like a distributed <em>Command Pattern</em>). A TransportChannel typically deals with some kind of networking mechanism (TCP sockets using BIO, using NIO, UDP / multicast, SSL over sockets, JXTA, EmberIO etc). See the <a href="https://activemq.apache. [...]
 
-<p>So the TransportChannel is basically concerned with sending and receiving <a href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/Command.html">Command</a> objects (each instance represents some kind of <em>command</em>). Packet is defined in the <a href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/package-summary.html">org.apache.activemq.command</a> package which defines all the JMS Messag [...]
+<p>So the TransportChannel is basically concerned with sending and receiving <a href="https://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/command/Command.html">Command</a> objects (each instance represents some kind of <em>command</em>). Packet is defined in the <a href="https://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/command/package-summary.html">org.apache.activemq.command</a> package which define [...]
 
 <h2 id="wireformat">WireFormat</h2>
 
@@ -118,11 +118,11 @@
 
 <p>So if you wish to provide your own binary, <em>on the wire</em> protocol then we just need a WireFormat implementation of your protocol, then we can use this with any transport (TCP BIO, NIO, JXTA etc).</p>
 
-<p>We use <a href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/openwire/OpenWireFormat.html">OpenWireFormat</a> by default which is the most efficient &amp; easiest format to use from Java code - so if both ends of the wire are Java then its highly recommended. Though other WireFormats are most welcome.</p>
+<p>We use <a href="https://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/openwire/OpenWireFormat.html">OpenWireFormat</a> by default which is the most efficient &amp; easiest format to use from Java code - so if both ends of the wire are Java then its highly recommended. Though other WireFormats are most welcome.</p>
 
 <h2 id="default-wire-format">Default Wire Format</h2>
 
-<p>The default wire format writes a byte which indicates the kind of Command which is being sent (see the <a href="http://activemq.apache.org/maven/5.5.0/activemq-core/apidocs/org/apache/activemq/command/CommandTypes.html">CommandTypes</a> interface which defines all the int constants for each type of command.</p>
+<p>The default wire format writes a byte which indicates the kind of Command which is being sent (see the <a href="https://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/command/CommandTypes.html">CommandTypes</a> interface which defines all the int constants for each type of command.</p>
 
 <p>The core JMS Message types each have a unique byte ID for</p>
 
@@ -135,16 +135,16 @@
   <li>StreamMessage</li>
 </ul>
 
-<p>Then in addition there are various other <a href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/package-summary.html">types of command</a> such as</p>
+<p>Then in addition there are various other <a href="https://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/command/package-summary.html">types of command</a> such as</p>
 
 <ul>
-  <li><a href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/ConnectionInfo.html">ConnectionInfo</a> for when a new connection is established with a message broker</li>
-  <li><a href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/ConsumerInfo.html">ConsumerInfo</a> when a new consumer is created on a connection</li>
-  <li><a href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/MessageAck.html">MessageAck</a> to acknowledge a message ID</li>
-  <li><a href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/TransactionInfo.html">TransactionInfo</a> to denote a transaction</li>
+  <li><a href="https://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/command/ConnectionInfo.html">ConnectionInfo</a> for when a new connection is established with a message broker</li>
+  <li><a href="https://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/command/ConsumerInfo.html">ConsumerInfo</a> when a new consumer is created on a connection</li>
+  <li><a href="https://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/command/MessageAck.html">MessageAck</a> to acknowledge a message ID</li>
+  <li><a href="https://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/command/TransactionInfo.html">TransactionInfo</a> to denote a transaction</li>
 </ul>
 
-<p>There are a few others; the <a href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/package-summary.html">org.apache.activemq.command</a> package describes them in their gory detail.</p>
+<p>There are a few others; the <a href="https://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/command/package-summary.html">org.apache.activemq.command</a> package describes them in their gory detail.</p>
 
 <p>Basically the DefaultWireFormat has a default encoding of each of these commands. So after the first byte which indicates the type of packet is written, there is a specific wire format per packet type.</p>
 
@@ -152,7 +152,7 @@
 
 <h1 id="message-broker">Message Broker</h1>
 
-<p>The APIs for the message broker (server side of the JMS client) are defined in the <a href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/broker/package-summary.html">org.apache.activemq.broker</a>. There are various other packages which define different parts, from the message stores to the message routing and so forth.</p>
+<p>The APIs for the message broker (server side of the JMS client) are defined in the <a href="https://activemq.apache.org/components/classic/documentation/maven/apidocs/org/apache/activemq/broker/package-summary.html">org.apache.activemq.broker</a>. There are various other packages which define different parts, from the message stores to the message routing and so forth.</p>
 
 <p>To see an overview of these packages try the <a href="docs">JavaDocs</a></p>
 


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@activemq.apache.org
For additional commands, e-mail: commits-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact