[ http://issues.apache.org/jira/browse/QPID-164?page=all ]
Martin Ritchie resolved QPID-164.
---------------------------------
Resolution: Fixed
New Revision: 486254
URL: http://svn.apache.org/viewvc?view=rev&rev=486254
Log:
QPID-164
JMSMapMessage.java - fixed incorrect exceptions and return values. Data now
sent as a Bytes message.
MapMessageTest.java - updated to be more through with the testing of the
returned message
EncodingUtils.java - added unsignedIntegerLength()
FieldTableFactory.java - removed specific PropertyFieldTable reference
PropertyFieldTable.java - fixed encoding issues that were causing
BufferOverflow errors.
PropertyFieldTableTest.java - added test to ensure that the encoding size is
correct for ALL types.
> MapMessage throws incorrect exceptions
> ---------------------------------------
>
> Key: QPID-164
> URL: http://issues.apache.org/jira/browse/QPID-164
> Project: Qpid
> Issue Type: Bug
> Components: Java Client, JMS Compliance
> Affects Versions: M1
> Reporter: Martin Ritchie
> Assigned To: Martin Ritchie
> Fix For: M2
>
>
> Currently Map Message throws NullPointer and exceptions these should all be
> MessageFormatExceptions.
> I had miss understood this bit of text from the API
> "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. "
> I had taken this to mean all null values even non-existent values. So if we
> end up with a null in the JMSMapMessage class we need to check if the key
> existed .. if so do the above valueOf(string) work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
