[esb-issues] [JBoss JIRA] Created: (JBESB-2664) HttpMessageComposer causing "org.xml.sax.SAXParseException: Content is not allowed in prolog."

[David Ward (JIRA)]

HttpMessageComposer causing "org.xml.sax.SAXParseException: Content is not allowed in prolog."
----------------------------------------------------------------------------------------------

                 Key: JBESB-2664
                 URL: https://jira.jboss.org/jira/browse/JBESB-2664
             Project: JBoss ESB
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Rosetta, Transports
    Affects Versions: 4.5
            Reporter: David Ward
            Assignee: David Ward
             Fix For: 4.6


In populateMesage(Message,T):void, if the request.getContentType() starts with "text/xml", then the payload should be set using a String constructed of the request bytes PLUS the request CHARACTER ENCODING.  Otherwise, a "org.xml.sax.SAXParseException: Content is not allowed in prolog." is thrown.  Actually, anthing starting with "text/" should construct a String with the appropriate character encoding.  If the content type doesn't start with "text/", then it should default to just setting the raw bytes as the payload.

-- 
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