You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Suresh Kodichath (JIRA)" <qp...@incubator.apache.org> on 2006/12/28 20:05:21 UTC
[jira] Updated: (QPID-231) QueueSession.createSender() should allow
a null Queue name.
[ http://issues.apache.org/jira/browse/QPID-231?page=all ]
Suresh Kodichath updated QPID-231:
----------------------------------
Attachment: QueueSenderAdapterPatch.patch
I have attached the patch file containing a fix for this issue. Appreciate if anybody with commit permissions can apply this patch to the trunk. Thanks!.
> QueueSession.createSender() should allow a null Queue name.
> -----------------------------------------------------------
>
> Key: QPID-231
> URL: http://issues.apache.org/jira/browse/QPID-231
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Suresh Kodichath
> Attachments: QueueSenderAdapterPatch.patch
>
>
> AMQ(JMS)Session::createSender() should allow for a null Queue name, as per the JMS specification. Currently while Qpid allows QueueSenderAdapter to be created with a null queue_name, any usage of this QueueSenderAdapter raises an Exception. For example: QueueSenderAdapter::setTimeToLive() on this new object will generate an UnsupportedOperationException("Queue is null"). This is not specific to TimeToLive which is not yet implemented.
> Removing the check for queue == null in checkPreConditions fixes this issue, and the tests pass as well for using it this way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira