[
https://issues.apache.org/activemq/browse/SM-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47526#action_47526
]
Ron Gavlin commented on SM-1697:
--------------------------------
Oops, it appears my test case is bad. It should be setting property
JbiConstants.DATESTAMP_PROPERTY_NAME with a java.util.Date object instead of a
Calendar object. This is what we are seeing in my real-world scenario when the
JMSException gets thrown. It appears a java.util.Date object will pass thru the
simple type filter. According to the JMS spec, (see the "Message Properties"
section of http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html)
java.util.Date is not a valid JMS Message Property.
Based on this document, it appears the simple type filter should be written
based on the following statement:
"The setObjectProperty method accepts values of class Boolean, Byte, Short,
Integer, Long, Float, Double, and String. An attempt to use any other class
must throw a JMSException."
So, either we automatically exclude values not specified in the above list, or
we take responsibility for marshalling specific types like java.util.Date. What
are your thoughts?
/Ron
> new smx-jms marshaler throws exception attempting to copy property
> "JbiConstants.DATESTAMP_PROPERTY_NAME" from NMR to JMS
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1697
> URL: https://issues.apache.org/activemq/browse/SM-1697
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jms
> Affects Versions: servicemix-jms-2008.01
> Reporter: Ron Gavlin
> Attachments: sm-1697.patch
>
>
> New smx-jms marshaler throws exception attempting to copy property
> "JbiConstants.DATESTAMP_PROPERTY_NAME" from NMR to JMS.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
