By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
The easiest way would be to use XPATH to check the existence of the SOAP envelope element in the message. Or, instead of using XPath, you could look at the document element (getDocument()->getFirstChild() in DOM speak, IIRC) and see if it's <soap:envelope xmlns:soap="..."/>. If there's no envelope, there's no SOAP. Since, presumably, you've got to parse the message anyway, I'd wager that's a more convenient way.
That said, in SOAP 1.1, the SOAPAction HTTP header is supposed to be present, though it has no particular required value ("to express the intent of the message"). You might check your vendor's SOAP implementation to verify this. So, without parsing the message, one could simply check for the presence of the SOAPAction HTTP header. That's probably a little less fault-tolerant, but "officially" correct. In general, if it's present, you most likely have a SOAP message. If it's not present, then you should check the root element of the document).
In SOAP 1.2(XMLP), the media type may be "application/soap+xml", so that can be used as an indicator as well. However, as with SOAPAction, at least at this point in the XMLP design, the application/soap+xml media type is not required. So if it is missing (as with SOAPAction above), you would still have to check the root element of your XML message (presuming, of course, that your message is XML -- if not, well, that's a different matter).
Dig Deeper on Service-oriented architecture (SOA)
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.