soap - What's the difference between MTOM and the attachment features provided by SAAJ? -


saaj: soap attachments api java

mtom: soap message transmission optimization mechanism

my simple understanding: deal soap attachments, mtom being more optimized version of saaj. correct?

are 2 different ways of doing same thing? or trying compare apples , oranges here?

can use saaj , mtom together?

it little bit more complicated. saaj old java api used manipulate soap envelopes, sending binary attachments can done in sane way (that not base64 encoded string in message body). saaj sort of low level interface, need construct soap envelope "by hand" in code , add attachments it.

if don't need work legacy code , want work directly soap envelopes, on jax-ws dispatcher , provider interfaces.

mtom beast. not full web service api - specialized way of sending attachments. can used "true" web service api jax-ws or saaj (if manage force saaj work way).

mtom (almost) used xop, more efficient way send binary data, compared base64 (which has large overhead). attachment sent separately mime attachment , mime type handled (that used issue java-microsoft technologies interactions).

nowdays forget saaj, use jax-ws + mtom support provided jax-ws implementations.


Comments

Popular posts from this blog

sql - VB.NET Operand type clash: date is incompatible with int error -

SVG stroke-linecap doesn't work for circles in Firefox? -

python - TypeError: Scalar value for argument 'color' is not numeric in openCV -