[jira] [Commented] (NIFI-7015) ConsumeJMS should handle any message type

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015434#comment-17015434 ] 

ASF subversion and git services commented on NIFI-7015:
-------------------------------------------------------

Commit 103325354b6930bf92e0f99b332866cbb2ffeb31 in nifi's branch refs/heads/master from Tamas Palfy
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1033253 ]

NIFI-7015 - ConsumeJMS now supports ObjectMessage, MapMessage and StreamMessage types as well. Added optional ERROR_QUEUE property. Result flowfiles get a 'jms.messagetype' attribute that contains the incoming message type (TextMessage, BytesMessage, ObjectMessage, MapMessage or StreamMessage).


> ConsumeJMS should handle any message type
> -----------------------------------------
>
>                 Key: NIFI-7015
>                 URL: https://issues.apache.org/jira/browse/NIFI-7015
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Pierre Villard
>            Assignee: Tamas Palfy
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> At the moment {{ConsumeJMS}} only handles {{TextMessage}} and {{ByteMessage}}. Support for {{StreamMessage}}, {{ObjectMessage}} and {{MapMessage}} should be added. Besides, there could be additional message types implementing the interface like {{ActiveMQBlobMessage}}.
> Supporting this would require extra work as this depends of the JMS providers. A property {{ERROR_QUEUE}} should be added to re-route the messages into another queue when there is no way to process the messages in the processor so that unsupported and/or malformed messages are still acknowledged and moved somewhere else without further blocking message processing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)