One of our B2B partners using a Seeburger connector is having problems processing our ebMS SOAP messages.
The messages are typical MIME encoding SOAP. The SOAP envelope and attached payload are NOT wrapped or 'pretty-printed'. They are sent as a single 'line' or stream.
It seems that within their server, these lines are being truncated to 512 bytes (and they are having parser errors as an added insult.)
Whether this is occuring in their ebMS server or in a front-end/proxy, I have no way of knowing.
They are wanting me to limit our message line length to 512 bytes... which is simply not going to happen...
No other partner has issues with this (and we have others using Seeburger)
Anyone here that's familiar with this have any thoughts?
Thanks for any ideas you can share.
- rich