[GitHub] activemq-artemis issue #1820: [ARTEMIS-550] fix up test to validate CORE and...

[michaelandrepearce <gi...@git.apache.org>]

Github user michaelandrepearce commented on the issue:

    https://github.com/apache/activemq-artemis/pull/1820
  
    @mattrpav i pinged on IRC but no response.
    
    From the JIRA i see you raised three points.
    
    
    > Consumption is in a different destination altogether
    
    As noted already a core queue is used for delivery either sharing a core queue (as like a JMS Queue, or JMS 2.0 Shared subscription) or having a core queue per consumer (as like JMS Topic consumer - non shared).
    
    > Consumption is handled by a queue-- which supports wider range of consuming options-- exclusive consumer, etc.
    
    In Artemis a jms 2.0 shared subscription is a queue (note this is part of the core model) on this core queues are possible to set this up with max consumers = 1 to represent an exclusive consumer.
    
    
    > Client-consumers drive the behavior without the need for server-side configuration
    
    Exactly the point of JMS 2.0 Topics, here you can send to a topic, and now you can get either queue like consuming semantics by using Shared Durable Subscription, or you can have JMS 1.1 pub sub semantic using standard Topic Consumer.
    
    
    On that note, i think if anything more is needed (such as if an address or queue is not found, detailing the requested routing type) it should be done with extending the FQQN which overrides the protocol managers, not by changing the core client just to blindly do something breaking others.



---