You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org> on 2009/02/09 05:48:59 UTC
[jira] Commented: (QPID-1654) Provide support to declare and bind a
queue to any exchange type using the javax.jms.Destination abstraction
[ https://issues.apache.org/jira/browse/QPID-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671728#action_12671728 ]
Rajith Attapattu commented on QPID-1654:
----------------------------------------
The AMQAnyDestination described above has been commited in to trunk at rev 742250
Further discussion is needed for exploring the best possible way of expressing declare and bind arguments in the JNDI file.
> Provide support to declare and bind a queue to any exchange type using the javax.jms.Destination abstraction
> ------------------------------------------------------------------------------------------------------------
>
> Key: QPID-1654
> URL: https://issues.apache.org/jira/browse/QPID-1654
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: M5
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: M5
>
>
> In order to support JMS 1.0 the Qpid implementation binds queues to the direct exchange to for JMS Queue and to topic exchange for JMS Topic.
> The JMS 1.1 spec provides a javax.Destination as an abstraction to represent any type of vendor destination.
> The abstract class AMQDestination has most of the functionality to support declaring and binding a queue to any destination.
> For starters it would be good to have an "AMQAnyDestination" class which simply takes in a binding URL in the constructor and a constructor which takes individual parameters that makes up the binding URL (for programatic constuction).
> Currently the fanout exchange is supported via the AMQQueue impl, which is a bit of hack, as AMQQueue is intended to support to the JMS Queue defined in JMS 1.0.
> Therefore it would be be best to support fanout exchange and other types of destinations using the above defined class.
> Using this class we could easily support Headers exchange, Failover exchange, XML exchange ..etc
> Also this class would make the current AMQHeadersExchange class redundent.
> As the next step we could think about how to express the declare and bind arguments using the binding URL format in the jndi props file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org