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

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

But Session.createTopic("TEST") doesn't actually create a topic on the broker, 
it is just creating a JMS Object for a destination which has been 
administratively created for you.  The name of the topic is something that the 
broker owns, and different broker implementations may make different 
restrictions on the form of that name.  In AMQP terms, all Topic T = 
Session.createTopic(X) just tells the client that any Producers/Consumers 
created for T should attempt to link to address X.
                
> 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