[
https://issues.apache.org/jira/browse/CAMEL-5429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408610#comment-13408610
]
BJ Peter DeLaCruz edited comment on CAMEL-5429 at 7/7/12 9:53 AM:
------------------------------------------------------------------
Before I used "jmsMessageType=Object", the application was sending null in a
message, and it worked. However, I ran into a problem when I was trying to send
a map of non-primitive, serialized objects. (See CAMEL-5293.) Using
"jmsMessageType=Object" solved CAMEL-5293, but now I can no longer send null in
a message as an exception will be thrown.
was (Author: bjpeter):
Before I used "jmsMessageType=Object", the application was sending null in
a message, and it worked. However, I ran into a problem when I was trying to
send a map of non-primitive, serialized objects. (See CAMEL-5293.) Using
"jmsMessageType=Object" solved CAMEL-5293, but now I can no longer send null in
a message.
> Sending null in body when forcing JMS message type to Object throws an
> Exception
> --------------------------------------------------------------------------------
>
> Key: CAMEL-5429
> URL: https://issues.apache.org/jira/browse/CAMEL-5429
> Project: Camel
> Issue Type: Bug
> Affects Versions: 2.9.0
> Reporter: BJ Peter DeLaCruz
> Attachments: Exception.txt, TestCamelJmsWithNull.java
>
>
> I set "jmsMessageType=Object", and when I try to send a null in the body, I
> get an exception. See program and log.
--
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
