Uploaded image for project: 'Spring AMQP'
  1. Spring AMQP
  2. AMQP-60

Add namespace support for defining Exchanges, Queues and Bindings

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Complete
    • Affects Version/s: None
    • Fix Version/s: 1.0.0.M3
    • Component/s: Core
    • Labels:
      None

      Description

      In the simplest case we could have separate elements all at top-level, including <binding>:

      <direct-exchange name="e" .../>
      
      <queue name="q" .../>
      
      <binding from="e" to="q" with="foo"/>
      

      However, it might be clearer to provide a hierarchical model where bindings are more implicit. One advantage of this approach would be the ability to have different semantics for different top-level exchange types (e.g. no routing-key for FanoutExchanges, key/value matching for HeaderExchanges, etc.)

      <direct-exchange name="e">
          <bindings routing-key="foo">
              <queue name="q"/>
          </bindings>
      </direct-exchange>
      

        Attachments

          Activity

            People

            • Assignee:
              david_syer Dave Syer
              Reporter:
              mark.fisher Mark Fisher
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: