[
https://issues.apache.org/jira/browse/QPID-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kennedy closed QPID-2680.
Closing issue. However, should point out that the doxygen build of pdfs from
docbook xml source is
The JMS client now defaults to using the new Address syntax developed for
the Qpid Messaging API (as used by the C++ client for example). See
http://qpid.apache.org/books/0.8/Programming-In-Apache-Qpid/html/index.html
for more details.
Alternatively you should be able to force usage of the old
Disconnected operation is a pain
Key: QPID-2978
URL: https://issues.apache.org/jira/browse/QPID-2978
Project: Qpid
Issue Type: Improvement
Components: C++ Client, Python Client
Thanks for the info,
It might be good to add the prefixing option in the docs, as just reading
the docs suggests automatically backward compatiability
(
http://qpid.apache.org/books/0.8/Programming-In-Apache-Qpid/html/ch03s02.html#id3084791
).
I'm also looking at how to translate the old fanout
Never mind, I found others having the same problem and already have a
example in the post.
Thanks,
Tim
On Tue, Dec 14, 2010 at 1:17 PM, Tim Chen t...@evri.com wrote:
I can't seem to figure out how to declare fanout for the producer using the
new address format.
Any examples how this can be
I've recently spent some time using the new API. I'm a big fan, but I
have a problem.
My app involves multiple long-lived server components in occasional
communication. In general, the components should start and keep running
whether or not the broker they use to communicate is up.
The
