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

This closes #69 - doc updates

This commit is contained in:
jbertram 2015-01-20 13:56:56 -06:00
parent 5364ad32f4 d2b668adf3
commit 98153ec1da
3 changed files with 1775 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/user-manual/en/architecture.md
View File

@ -126,8 +126,8 @@ The standard stand-alone messaging server configuration comprises a core
messaging server and a JMS service.
The role of the JMS Service is to deploy any JMS Queue, Topic and
ConnectionFactory instances from any server side `activemq-jms.xml`
configuration files. It also provides a simple management API for
ConnectionFactory instances from any server side JMS
configuration. It also provides a simple management API for
creating and destroying Queues and Topics
which can be accessed via JMX or the connection. It is a separate
service to the ActiveMQ core server, since the core server is JMS

2
docs/user-manual/en/client-reconnection.md
View File

@ -36,7 +36,7 @@ to the client, and the client can then free up space in the buffer.
If you are using JMS and you're using the JMS service on the server to
load your JMS connection factory instances into JNDI then this parameter
can be configured in `activemq-jms.xml` using the element
can be configured in the jms configuration using the element
`confirmation-window-size` a. If you're using JMS but not using JNDI
then you can set these values directly on the
`ActiveMQConnectionFactory` instance using the appropriate setter

1780
docs/user-manual/en/configuration-index.md
View File

File diff suppressed because it is too large Load Diff