[CXF-3748] Using Dispatch API with SOAPMessage type fails to set WS-Addressing action header properly if there's whitespace after the soap:body

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.4.1
• Fix Version/s: 2.3.7, 2.4.3
• Component/s: JAX-WS Runtime
• Labels: dispatch soapmessage ws-addressing
• Estimated Complexity: Novice
• Assignee: Daniel Kulp
• Reporter: Jesse Pangburn
• Created: 18/Aug/11 00:02
• Updated: 06/Sep/11 20:49
• Resolved: 19/Aug/11 02:08

Description

if you use a SOAPMessage instead of a Source then the following function fails (ignoring the exception) and your ws-addressing action doesn't get set- if you have any whitespace after the soap:body element before your first payload element:
private String getPayloadElementName(SOAPMessage soapMessage) {
try

{ SOAPElement element = (SOAPElement)soapMessage.getSOAPBody().getChildElements().next(); return new QName(element.getNamespaceURI(), element.getLocalName()).toString(); }

catch (Exception e)

{ //ignore }

return null;

}

This fails because the .next() call at the end gets a text node instead of an element object so the cast fails. So inexplicably your ws-addressing action header doesn't get set as far as the user sees.