I understand soap over http mode uses http post under the covers and I read http post has a max size of 2 mb data.
Does this mean the max size of a soap payload inline not considering MIME attachments is 2 mb.
I am currently evaluating a scenario where in we need to bundle a lot of xml data in the SOAP request payloads.
Embedding massive amounts of xml inside a SOAP body is a disaster for performance both on the server and client side. Reason being that the server has to build this huge DOM in memory and the client has to parse it.
(History of SOAP mode) One of the major objections SUN had to the original SOAP concept was in fact exactly that disaster. It wasn't until SOAP attachments SAAJ was defined that SUN got on the SOAP bandwagon (/History of SOAP mode)
Time for you to step back and rethink your architecture.
So I can use SAAJ to pass a document containing xml payloads in the attachment (does not have to be Soap tagged but pure xml structure payload).
and then also construct the SOAP response to include a xml document based response as attachment using SAAJ.
When SOAP was just getting started, I saw lots of developers totally shocked by how long it took for their service to run - turned out they were trying to send big messages as part of the SOAP body.
Joined: Oct 23, 2003
Sorry for my novice SAAJ questions but I did not get a clear understanding on the material available online for SAAJ. Most of them talk about how the client can attach a document using SAAJ but did not see specifics on how the server side Web service should process a SAAJ attachment to service a request.
In my case we already have a web service implementation in place. I understand there should not be any changes required to the signature of the current web service but a SAAJ attachment can be included seamlessly and on the server side have extra code to intercept and process the SAAJ attachment.
I would appreciate if someone could share pointers on the SAAJ server side processing part.