[esb-issues] [JBoss JIRA] Closed: (JBESB-2517) Http Gateway should support request data decoding

[ https://jira.jboss.org/jira/browse/JBESB-2517?page=com.atlassian.jira.plu... ] Tom Fennelly closed JBESB-2517. ------------------------------- Resolution: Done JBESB_4_4_GA_FP: 25994 The HttpMessageComposer now looks at the Content-Type header and matches it against the "org.jboss.soa.esb.mime.text.types" config in the jbossesb-properties.xml. This config specifies a semi-colon separated list of mime type patterns that we interpret as being a text mime-type (default value is "text/*;application/xml;application/*-xml"). If the content type on the request equals this, the message payload is decoded and bound on the ESB Message as a String. If it doesn't find a match in this config, the payload is bound as a byte[] (i.e. un-decoded). The <http-listener> config also supports a "payloadAs" attribute that can override the above Content-Type processing. It can be set to "STRING" or "BYTES". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira