Hi Simon, You are right, TUSCANY-2207 had issues and this is been fixed now.
On Thu, Nov 13, 2008 at 6:11 PM, Simon Laws <[EMAIL PROTECTED]>wrote: > Hi Ram > > Somehow I missed this from a few days ago. Apologies. Comments in line. > > Simon > > On Thu, Nov 6, 2008 at 7:50 AM, Ramkumar R <[EMAIL PROTECTED]> wrote: > >> Support for Axis2 MTOM is now enabled with fixes available from >> TUSCANY-2611 following the check-in made using TUSCANY-2207 (we does not >> seem to working). > > > Do you mean here that there were problems with TUSCANY-2207 and you have > fixed them or that there are still outstanding problems? From your comments > below I assume the former. > >> >> >> As discussed in thread... >> http://www.mail-archive.com/[EMAIL PROTECTED]/msg26726.html >> >> <binding.ws requires="MTOM"/> >> >> can be used to enable the MTOM optimization on the client/server side. >> >> Enabling MTOM Optimization on the Client Side: >> To enable MTOM optimization on the client side <binding.wsrequires="MTOM"/> >> should be used with the reference bindings. By enabling >> this feature, any SOAP envelope, regardless of whether it contains >> optimizable content or not, will be serialized as an MTOM optimized MIME >> message. > > > Sounds good. I'd like to review with you whether this should also exploit > the wire format approach. I'll take a look at how it works now before > commenting more on this. > > >> >> >> Enabling MTOM Optimization on the Server Side: >> The Axis 2 server automatically identifies incoming MTOM optimized >> messages based on the content-type and de-serializes them accordingly. The >> user can enable MTOM on the server side for outgoing messages. To enable >> MTOM optimization on the server side <binding.ws requires="MTOM"/> should >> be used with the service bindings. >> >> A junit test is available as part of binding-ws-axis2 module to demostrate >> the same. [ >> http://svn.apache.org/repos/asf/tuscany/java/sca/modules/binding-ws-axis2/src/test/java/org/apache/tuscany/sca/binding/ws/axis2/itests/mtom/ >> ] >> >> NOTE: Any change in behaviour is not noticed through the testcase as >> change is only noticed in the SOAP Envelope messages when MTOM is enabled. >> What you can notice is that the MTOMStAXSOAPModelBuilder is used instead >> StAXSOAPModelBuilder as the builder for SOAP messages for the >> content-type:application/xop+xml. >> >> -- >> Thanks & Regards, >> Ramkumar Ramalingam >> > > -- Thanks & Regards, Ramkumar Ramalingam
