diff options
| -rw-r--r-- | qpid/doc/book/src/jms-client-0-8/JMS-Client-Understanding.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/qpid/doc/book/src/jms-client-0-8/JMS-Client-Understanding.xml b/qpid/doc/book/src/jms-client-0-8/JMS-Client-Understanding.xml index 7113831f04..3b449e8034 100644 --- a/qpid/doc/book/src/jms-client-0-8/JMS-Client-Understanding.xml +++ b/qpid/doc/book/src/jms-client-0-8/JMS-Client-Understanding.xml @@ -333,7 +333,7 @@ amqp://guest:guest@clientid/?brokerlist='localhost:5671?trust_store='/path/to/ap >Session#createTopic()</ulink> accepts either a topic name, or a Binding URL. If only name is specified the destination will be resolved into binding URL: topic://amq.topic//<topic name>?routingkey=’<topic name>’.</para> - <para>Calling Session#createTopix() has no effect on the Broker.</para> + <para>Calling Session#createTopic() has no effect on the Broker.</para> <para>Reiterating the advice from the JMS javadoc, it is suggested that this method is not generally used. Instead, application should lookup Destinations declared within JNDI.</para> </section> |