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
{{ message }}
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
In Sekken::Message and Sekken::EnvelopeBuilder::XmlMarkup is instantiated with margin and indent values, which are used when emitting the XML. Unfortunately some SOAP servers (case-in-point: MS Navision) is pretty finicky about the way requests are formatted, and any extraneous whitespace yields an Invalid SOAP request error.
I understand margins and indentations help emitting a cleaner output (e.g. when using operation#build); should we consider making this configurable somehow?
The text was updated successfully, but these errors were encountered:
mbrung
changed the title
Remove indentation and margin from Builder calls
Remove indentation and margin from Builder::XmlMarkup calls
Apr 15, 2015
mbrung
added a commit
to mbrung/sekken
that referenced
this issue
Sep 10, 2015
In
Sekken::Message
andSekken::Envelope
Builder::XmlMarkup
is instantiated withmargin
andindent
values, which are used when emitting the XML. Unfortunately some SOAP servers (case-in-point: MS Navision) is pretty finicky about the way requests are formatted, and any extraneous whitespace yields anInvalid SOAP request
error.I understand margins and indentations help emitting a cleaner output (e.g. when using
operation#build
); should we consider making this configurable somehow?The text was updated successfully, but these errors were encountered: