This closes #69 - doc updates
This commit is contained in:
commit
98153ec1da
|
@ -126,8 +126,8 @@ The standard stand-alone messaging server configuration comprises a core
|
||||||
messaging server and a JMS service.
|
messaging server and a JMS service.
|
||||||
|
|
||||||
The role of the JMS Service is to deploy any JMS Queue, Topic and
|
The role of the JMS Service is to deploy any JMS Queue, Topic and
|
||||||
ConnectionFactory instances from any server side `activemq-jms.xml`
|
ConnectionFactory instances from any server side JMS
|
||||||
configuration files. It also provides a simple management API for
|
configuration. It also provides a simple management API for
|
||||||
creating and destroying Queues and Topics
|
creating and destroying Queues and Topics
|
||||||
which can be accessed via JMX or the connection. It is a separate
|
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
|
service to the ActiveMQ core server, since the core server is JMS
|
||||||
|
|
|
@ -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
|
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
|
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
|
`confirmation-window-size` a. If you're using JMS but not using JNDI
|
||||||
then you can set these values directly on the
|
then you can set these values directly on the
|
||||||
`ActiveMQConnectionFactory` instance using the appropriate setter
|
`ActiveMQConnectionFactory` instance using the appropriate setter
|
||||||
|
|
File diff suppressed because it is too large
Load Diff
Loading…
Reference in New Issue