Apache
/
activemq-artemis
mirror of https://github.com/apache/activemq-artemis.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

ARTEMIS-4043: remove other doc snippets linking to previously-removed rest.md file, also update URL to point to referenced version

This commit is contained in:
Robbie Gemmell 2022-10-12 15:15:29 +01:00
parent e951ce67ca
commit b604545a3c
5 changed files with 3 additions and 54 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
docs/user-manual/en/messaging-concepts.md
View File

@ -194,27 +194,6 @@ the JMS API.
Please see [Core](core.md) for using the Core API with Apache ActiveMQ Artemis.
### RESTful API
[REST](https://en.wikipedia.org/wiki/Representational_State_Transfer)
approaches to messaging are showing a lot interest recently.
It seems plausible that API standards for cloud computing may converge on a
REST style set of interfaces and consequently a REST messaging approach is a
very strong contender for becoming the de-facto method for messaging
interoperability.
With a REST approach messaging resources are manipulated as resources defined
by a URI and typically using a simple set of operations on those resources,
e.g. PUT, POST, GET etc. REST approaches to messaging often use HTTP as their
underlying protocol.
The advantage of a REST approach with HTTP is in its simplicity and the fact
the internet is already tuned to deal with HTTP optimally.
Please see [Rest Interface](rest.md) for using Apache ActiveMQ Artemis's
RESTful interface.
### AMQP
[AMQP](https://en.wikipedia.org/wiki/AMQP) is a specification for interoperable

3
docs/user-manual/en/protocols-interoperability.md
View File

@ -24,9 +24,6 @@ Although JMS and Jakarta Messaging are standardized APIs, they does not define a
[JMS & Jakarta Messaging clients](using-jms.md) are implemented on top of the core protocol. We also provide a
[client-side JNDI implementation](using-jms.md#jndi).
The broker also ships with a [REST messaging interface](rest.md) (not to be confused with the REST management API
provided via our integration with Jolokia).
## Configuring Acceptors
In order to make use of a particular protocol, a transport must be configured with the desired protocol enabled. There

26
docs/user-manual/en/security.md
View File

@ -1516,32 +1516,6 @@ connection factories in a resource adapter:
These properties, once specified, are eventually set on the corresponding
internal factories.
### Config for REST interface
Apache Artemis REST interface ([Rest](rest.md)) allows interactions between jms
client and rest clients. It uses JMS ObjectMessage to wrap the actual user
data between the 2 types of clients and deserialization is needed during this
process. If you want to control the deserialization for REST, you need to set
the black/white lists for it separately as Apache Artemis REST Interface is
deployed as a web application. You need to put the black/white lists in its
web.xml, as context parameters, as follows
```xml
<web-app>
<context-param>
<param-name>org.apache.activemq.artemis.jms.deserialization.whitelist</param-name>
<param-value>some.allowed.class</param-value>
</context-param>
<context-param>
<param-name>org.apache.activemq.artemis.jms.deserialization.blacklist</param-name>
<param-value>some.forbidden.class</param-value>
</context-param>
...
</web-app>
```
The param-value for each list is a comma separated string value representing the list.
## Masking Passwords
For details about masking passwords in broker.xml please see the [Masking

2
docs/user-manual/en/versions.md
View File

@ -44,7 +44,7 @@ Highlights:
#### Upgrading from older versions
1. We removed the *-all clients from ./lib/client in the assembly as part of [ARTEMIS-4006](https://issues.apache.org/jira/browse/ARTEMIS-4006). If you use these libraries they can be found at Maven Central, please refer to the [client class path documentation](client-classpath.md) for more information.
2. We removed ActiveMQ-Artemis rest as part of 2.26.0. If you still require activemq rest you can still have access to its latest version at [Maven central](https://mvnrepository.com/artifact/org.apache.activemq.rest/artemis-rest/2.25.0). You can still follow the steps on Rest from any [previous documentation](https://activemq.apache.org/components/artemis/documentation/2.24.0/rest.html), however you should stop using the module as it will not be maintained any more.
2. We removed ActiveMQ-Artemis rest as part of 2.26.0. If you still require activemq rest you can still have access to its latest version at [Maven central](https://mvnrepository.com/artifact/org.apache.activemq.rest/artemis-rest/2.25.0). You can still follow the steps on Rest from any [previous documentation](https://activemq.apache.org/components/artemis/documentation/2.25.0/rest.html), however you should stop using the module as it will not be maintained any more.
3. We removed web content from distribution and redirected to the console web requests with the root target as part of [ARTEMIS-3980](https://issues.apache.org/jira/browse/ARTEMIS-3980). If you used to customize the index page or to add custom content in the web folder please refer to the [web-server documentation](web-server.md) for more information on disabling the redirect and enabling the web content.
## 2.25.0

5
docs/user-manual/en/web-server.md
View File

@ -3,8 +3,7 @@
Apache ActiveMQ Artemis embeds the [Jetty web
server](https://www.eclipse.org/jetty/). Its main purpose is to host the [Management
Console](management-console.md). However, it can also host other web
applications like the [REST interface](rest.md) or even Spring-based web
applications (e.g. using Camel).
applications.
## Configuration
@ -133,4 +132,4 @@ Set the `customizer` attribute via the `web` element to enable the [`ForwardedRe
The embedded web server can be stopped, started, or restarted via any available
management interface via the `stopEmbeddedWebServer`, `starteEmbeddedWebServer`,
and `restartEmbeddedWebServer` operations on the `ActiveMQServerControl`
respectively.
respectively.