What do you think about attached DefaultMessageRenderer.patch instead of using bytes-as-text-message-renderer.patch?
As DefaultMessageRenderer is now capable to render bytes messages (HJMS-165) I suppose the separate renderer to render BytesMessage as text is not needed any more.
DefaultMessageRenderer.patch adds an ability for
DefaultMessageRenderer to use different encodings to render byte messages.
Sergey Zhemzhitsky [21/Sep/11 03:23 AM]
Hi Colin,
What do you think about attached DefaultMessageRenderer.patch instead of using bytes-as-text-message-renderer.patch?
As DefaultMessageRenderer is now capable to render bytes messages (HJMS-165) I suppose the separate renderer to render BytesMessage as text is not needed any more.
DefaultMessageRenderer.patch adds an ability for
DefaultMessageRenderer to use different encodings to render byte messages.
Yes thats better. I will think of a way to make the character sets a combo box rather than free text via CharSet.availableCharSets...? Perhaps by looking at the return type of the config bean and making it a CharSet rather than a String?
Colin Crist [21/Sep/11 04:00 PM]
Yes thats better. I will think of a way to make the character sets a combo box rather than free text via CharSet.availableCharSets...? Perhaps by looking at the return type of the config bean and making it a CharSet rather than a String?
Sergey Zhemzhitsky [22/Sep/11 09:07 AM]
Hi Colin,
>> Perhaps by looking at the return type of the config bean and making it a CharSet rather than a String
Sounds great.
New Feature
Open
Major
Renderer that is able to render BytesMessage as text
