Github user devriesb commented on a diff in the pull request: https://github.com/apache/nifi/pull/2458#discussion_r167252827 --- Diff: nifi-nar-bundles/nifi-jms-bundle/nifi-jms-processors/src/main/java/org/apache/nifi/jms/processors/PublishJMS.java --- @@ -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, Charset.defaultCharset())); --- 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.
---