[
https://issues.apache.org/jira/browse/QPID-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002023#comment-13002023
]
Rajith Attapattu commented on QPID-3108:
----------------------------------------
What you need here is to extend your test class using QpidBrokerTestCase. The
rest is taken care of for you.
You don't need to worry about whether it's in-vm , java broker or C++ broker as
the type of broker is determined by the respective test profile.
Add your test in the systests module and have a look at the
AddressBasedDestinationTest as an example.
Had you asked on the mailing list, it could have saved you 2 hours :)
> QueueSender incorrectly checks for null queue
> ---------------------------------------------
>
> Key: QPID-3108
> URL: https://issues.apache.org/jira/browse/QPID-3108
> Project: Qpid
> Issue Type: Bug
> Components: Java Client, JMS Compliance
> Affects Versions: 0.8
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
> Fix For: 0.9
>
>
> JMS documents that you can create a QueueSender with a null queue (called an
> unidentified queue in the documentation) and this is fine as long as you
> don't try to use one fo the send methods that relies on the queue being set
> up at construction time.
> The current code checks for null queue in the getters too and so causes
> erroneous UnsupportedOperationException exceptions to be throw when they are
> used with an unidentified queue.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
