You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I currently work around this issue, by removing the Header from the request body, before passing it on to the xsdata parser. I use the following code for this:
When generating SOAP messages from a WSDL, the
Envelope
for input and output defines only aBody
and noHeader
.Envelope specification: https://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383494
A generated SOAP message now looks like:
The Header element is missing here.
As a result, I am unable to parse incoming SOAP requests that I send from SOAP UI. The parser complains about the now unexpected Header element.
with the request message structure looking like:
Work-around
I currently work around this issue, by removing the Header from the request body, before passing it on to the xsdata parser. I use the following code for this:
This is not super efficient, since the XML gets deserialzed and serialzed to handle the removal of the Header from the request XML data.
The text was updated successfully, but these errors were encountered: