[ 
https://issues.apache.org/jira/browse/QPID-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709692#comment-13709692
 ] 

Rob Godfrey commented on QPID-4991:
-----------------------------------

For the AMQP 1-0 JMS client there is (in general) no meaning to the "topic://" 
prefix... AMQP 1-0 addresses are just strings.  I believe that ActiveMQ has 
some requirements around prefixing when used with our JMS client, but this is 
ActiveMQ specific.

When using the Qpid/Java broker, for example... one could use 
Session.createTopic("amq.direct") (or any other exchange name) to use the given 
exchange as a topic. 
                
> JMS AMQP 1.0 API Session.createTopic( "TEST" ) does not work as expected
> ------------------------------------------------------------------------
>
>                 Key: QPID-4991
>                 URL: https://issues.apache.org/jira/browse/QPID-4991
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: 0.22
>         Environment: all
>            Reporter: Axel Podehl
>
> I've read that AMQP topics should start with "topic://" prefix, but that's 
> really not JMS standard (compare TIBCO EMS or IBM MQSeries implementation). 
> If you create a consumer with Session.createTopic( "TEST" ), this call does 
> return a org.apache.qpid.amqp_1_0.jms.impl.TopicImpl, but when I publish to 
> it with a producer using Session.createTopic( "topic://TEST" ) the message is 
> not received.
> I think, the call to Session.createTopic( String dest ) should automatically 
> add the "topic://" prefix if it's not there such that createTopic() always 
> creates a working topic.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to