When we use the secured adaptor, it looks like the following (note how there is no semicolon after the soap+xml)
And we get this error when trying to process it (this is not Connect code base)
Error message was: Unable to internalize message
com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message
Adding a break point and modifying the content type to include a semicolon gets us past the error. Can you confirm whether the content type header is how you would expect?
Re: Is the content type header correct for secured MPI adaptor?
I too encountered this issue. I believe the issue lies with the WsAddressingServiceEndpointDecorator class. The removeActionFromContentType() method is called, is splitting the content-type by semicolon, but is never placing the semicolon(s) back in place when reconstructing the content-type after the action has been removed. I have a hacky fix in place in my test configuration, but a proper fix probably should be put in place.
RE: Is the content type header correct for secured MPI adaptor?
Google is my friendJ
@Duncan, the only work around would be to use unsecured or cherry pick the fix commit into your installation.
From: Chad Freeman [via CONNECT Forums] [mailto:ml-node+[hidden email]]
Sent: Wednesday, November 13, 2013 3:29 PM To: Weaver, Matthew (CGI Federal) Subject: Re: Is the content type header correct for secured MPI adaptor?
Looks good Matthew. Pretty slick with the regex. ;)
If you reply to this email, your message will be added to the discussion below: