[
https://issues.apache.org/activemq/browse/AMQ-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61305#action_61305
]
Gary Tully commented on AMQ-2840:
---------------------------------
I reverted the changes so the TCK will pass. I added a new method,
getAllPropertyNames() that returns all the properties, JMS standard props and
JMSX extension props, so folks who want this non standard behavior can have it
in an explicitly non portable way.
My bad on this late change, not sure it would have been avoided if I validated
against the spec though, I would have taken Eugene's interpretation.
What is the expected drop date for Geronimo, it makes sense to cut a new
release for the next 2.2.x release. Think it may also makes sense to wait some
time to ensure there are no other must fix issues.
> JMSX Properties not returned from message.propertyExists() and
> message.getPropertyNames()
> -----------------------------------------------------------------------------------------
>
> Key: AMQ-2840
> URL: https://issues.apache.org/activemq/browse/AMQ-2840
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.0
> Reporter: Andriy Hnativ
> Assignee: Gary Tully
> Fix For: 5.4.1
>
> Attachments: patch.txt
>
>
> Methods propertyExists() and getPropertyNames() defined in the class
> org.apache.activemq.command.ActiveMQMessage (activemq-core) return only
> custom properties. The JMSX properties (like JMSXDeliveryCount) are not being
> returned. This problem exists not only for a new version of ActiveMQ (5.4),
> but also for 5.3 (and probably for others as well).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
