[
https://issues.apache.org/jira/browse/QPID-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050577#comment-13050577
]
Rajith Attapattu commented on QPID-3273:
----------------------------------------
I already noticed that the broker does not depend on the JMS spec jar and fixed
that - but thanks for pointing it out.
It seems the anyedit plugin is somewhat doing the exact opposite with the tabs
:)
I will fix the log statements to probably include both.
As for using constants for PERSISTENT and NON_PERSISTENT, I will check to see
if we have any existing constants.
If it doesn't exist, I am wondering where to include the constants. Do you know
of an existing class that contains constants?
I am not too keen to add a new class just for this.
> JMSDeliveryMode has to be used as a string in a selector
> ---------------------------------------------------------
>
> Key: QPID-3273
> URL: https://issues.apache.org/jira/browse/QPID-3273
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.6, 0.8, 0.10
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Priority: Minor
> Fix For: 0.11
>
> Attachments: QPID-3273.patch
>
>
> Section 3.8.13 of the JMS spec says that JMSDeliveryMode has to be used as a
> string in a selector (i.e. JMSDeliveryMode = 'PERSISTENT').
> But Qpid only supports it as an integer (i.e JMSDeliveryMode = 2).
--
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]
