[
https://issues.apache.org/jira/browse/QPID-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207335#comment-13207335
]
Rajith Attapattu commented on QPID-3838:
----------------------------------------
Simply changing the existing behaviour can break existing applications.
One solution is to check the "strict-jms" flag and convert the property name to
allow the TCK to pass.
i.e if the flag is present, "qpid.subject" will be converted to
"JMS_qpid.subject".
(This is done on the receiving side, so nothing would change on the wire)
Applications could still continue to use "qpid.subject" to retrieve the subject
and the code internally will resolve to "JMS_qpid.subject".
Perhaps there is a more elegant way to solve this issue. Comments are welcome !
> [JMS] Vendor specific properties should be prefixed with JMS_
> -------------------------------------------------------------
>
> Key: QPID-3838
> URL: https://issues.apache.org/jira/browse/QPID-3838
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.12, 0.14
> Reporter: Rajith Attapattu
> Priority: Minor
> Fix For: 0.15
>
>
> As per the JMS spec, vendor specific message properties should be prefixed
> with "JMS_"
> Since we are including "qpid.subject" in all outgoing messages, it's causing
> a TCK failure.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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:dev-subscr...@qpid.apache.org
