You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org> on 2007/02/17 00:13:05 UTC
[jira] Resolved: (QPID-375) Remove assumptions on amq.topic and
amq.direct being the default (and only) topic and direct exchanges
[ https://issues.apache.org/jira/browse/QPID-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Godfrey resolved QPID-375.
------------------------------
Resolution: Fixed
Resolved at revision 508649
> Remove assumptions on amq.topic and amq.direct being the default (and only) topic and direct exchanges
> ------------------------------------------------------------------------------------------------------
>
> Key: QPID-375
> URL: https://issues.apache.org/jira/browse/QPID-375
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Rob Godfrey
> Assigned To: Rob Godfrey
> Priority: Minor
>
> There are a number of places in the Java client code where the exchange name for a Queue or Topic destination is either explictly or implicitly set to be amq.direct or amq.topic. We should allow other exchanges of the relevant class to be used instead.
> Because a number of API calls in JMS take a single string representing a queue or topic name; we need to establish a default queue exchange and a default topic exchange. I suggest adding these as options to the connection url, and if these options are not set , then falling back on amq.direct and amq.topic.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.