You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org> on 2009/03/19 22:57:50 UTC
[jira] Commented: (QPID-1760) Improve toString method for
JMSMessage
[ https://issues.apache.org/jira/browse/QPID-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683637#action_12683637 ]
Rajith Attapattu commented on QPID-1760:
----------------------------------------
I have commited a fix in Qpid trunk at rev 756228.
The AbstractBytesMessage will now use the toString method from AbstractJMSMessage
Also I have modified the toBodyString method in AbstractBytesMessage to use a function that can handle unprintable charachters and print contents upto a maximum of 100 bytes.
> Improve toString method for JMSMessage
> --------------------------------------
>
> Key: QPID-1760
> URL: https://issues.apache.org/jira/browse/QPID-1760
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.6
>
>
> Currently the toString method does not print any meaningful information for Byte, Stream or Map message.
> The AbstractJMSMethod is also not printing the replyTo (if available) and also printing the properties in one line which makes it a bit unreadable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org