[AMQ-1282] Bad conversion of nonexistent data in MapMessage

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.1.1
• Fix Version/s: 5.3.0
• Component/s: JMS client
• Assignee: Robert Davies
• Reporter: Elliotte Rusty Harold
• Created: 14/Jun/07 19:20
• Updated: 07/Jul/09 05:34
• Resolved: 07/Jul/09 05:34

Description

Consider simple reception code like this:

MapMessage message = (MapMessage) consumer.receive(1000);
int x = message.getInt("foo"));

I notice that x is now set to zero even though there was no "foo" value in the map. I would have expected an exception.

According to Gaurav Hariani <[e-mail]>

also from the spec api: http://java.sun.com/j2ee/1.4/docs/api/javax/jms/MapMessage.html

Attempting to read a null value as a primitive type must be treated as calling the primitive's corresponding valueOf(String) conversion method with a null value. Since char does not support a String conversion, attempting to read a null value as a char must throw a NullPointerException.

.. so you are right that it is a bug ... since Integer.valueOf(null) throws an Exception