Snolan,
Be careful with just setting the content-type to to something that “Works!” without knowing the implications. For example, if you set the content-type to application/x-www-form-urlencoded, one of the things that you’re telling the receiver is that your data is “URL-encoded.” Therefore, if you do not URL encode it and you happen to have a special character within the data (example, &), you will most likely run into an error.
Like Rob was saying, if all you want to do is to post an XML message to a Flow service from a Java application, then set your content-type to “text/xml” and send the XML in the body of the HTTP POST request. The IS content handler will then pass the XML as an XML node to your Flow service.
#webMethods#Integration-Server-and-ESB#webmethods-Protocol-and-Transport