Date: 2005-03-16T19:20:14 Editor: ThilinaGunarathne Wiki: Apache Web Services Wiki Page: Axis2/MTOM URL: http://wiki.apache.org/ws/Axis2/MTOM
no comment Change Log: ------------------------------------------------------------------------------ @@ -1,5 +1,5 @@ ##language:en -##language:en + Email: [EMAIL PROTECTED] @@ -18,15 +18,15 @@ '''T'''ransport module has given the responsibility of identifying MTOM messages and choosing between the right builder (MTOMStAXSOAPBuilder or StAXSOAPModelBuilder). Identifying MTOM messages can be done by looking at the �Content-Type� and �type� headers of the message. - || Content-Type: Multipart/Related;boundary=MIME_boundary; || - || type="application/xop+xml"; || + || Content-Type: Multipart/Related;boundary=MIME_boundary; || + || type="application/xop+xml"; || '''M'''TOMStAXSOAPBuilder assumes that the Input Stream provided to it contains an MTOM encoded MIME message. It passes that Input stream to MTOMBuilder. MTOMbuilder extracts the root mime part which contains the XOP soap message and returns a XMLStreamReader(parser) built using that Soap message to the MTOMStAXSOAPModelBuilder. This builder deferred builds the AXIOM using that parser. '''W'''hen the builder comes across an xop:include element with the correct namespace, it creates an OMBlob node in the AXIOM. This OMBlob node keeps the �CID� value read from xop:include element and a reference to the MTOMbuilder in it. - || <xop:Include xmlns:xop='http://www.w3.org/2004/08/xop/include' || - || href='cid:http://example.org/me.png'/> || + || <xop:Include xmlns:xop='http://www.w3.org/2004/08/xop/include' || + || href='cid:http://example.org/me.png'/> || [http://www.cse.mrt.ac.lk/~gunarnkt/MTOM/img/mtom2.jpg http://www.cse.mrt.ac.lk/~gunarnkt/MTOM/img/mtom2.jpg]
