ASF GitHub Bot commented on NIFI-2630:

Github user devriesb commented on a diff in the pull request:

    --- Diff: 
    @@ -131,4 +143,10 @@ protected JMSPublisher 
finishBuildingJmsWorker(CachingConnectionFactory connecti
             session.read(flowFile, in -> StreamUtils.fillBuffer(in, 
messageContent, true));
             return messageContent;
    +    private String extractTextMessageBody(FlowFile flowFile, 
ProcessSession session) {
    +        final StringWriter writer = new StringWriter();
    +        session.read(flowFile, in -> IOUtils.copy(in, writer, 
    --- End diff --
    i'm not sure if this is a helpful "middle ground" suggestion or not, but 
you could add a charset property that itself defaults to 
Charset.defaultCharset().  That way the out of the box behavior uses the 
charset specified for the jvm, but can be overridden on a per processor basis 
if needed.

> Allow PublishJMS processor to create TextMessages
> -------------------------------------------------
>                 Key: NIFI-2630
>                 URL: https://issues.apache.org/jira/browse/NIFI-2630
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 0.6.0
>            Reporter: James Anderson
>            Assignee: Michael Moser
>            Priority: Minor
>              Labels: patch
>         Attachments: 
> 0001-NIFI-2630-Allow-PublishJMS-processor-to-create-TextM.patch
> Create a new configuration option for PublishJMS that allows the processor to 
> be configured to emit instances of TextMessages as well as BytesMessage.

This message was sent by Atlassian JIRA

Reply via email to