About this topic. I'd like to ask somethings that tomorrow i wish to implement. The Axis MTOM at client side is easy: 1) If you enable in Axis ServiceClient's Options whenever you send a SOAP Envelope with base64encode. It becomes MTOM attachment. Here I've a question. If enableMTOM is enabled should i convert to base64 current SOAP Envelope, replacing current nodes with OMText containing base64, so that the support will be able to MTOMize it? (I think NO, but I'd like to have confirm on this). 2) Axis recognizes automatically all incoming MTOM at server side.
More difficult (but a just bit more) is about outgoing messages. From axis docs it seems that you should enable it in configuration. My idea is to enable it optionally. With this: <parameter name="enableMTOM">optional</parameter> Axis2 will respond with a MTOMised message if the request message was a mtomised message. Axis2 will respond with a non-MTOMised message if the request message was a non-mtomised message. Also this does not take in to the account whether there is an attachment outgoing message or not. Is that ok for you? Ciao, Giorgio. --- Giorgio Zoppi [EMAIL PROTECTED] You're not your job. You're not how much money you have in the bank. You're not the car you drive. You're not the contents of your wallet. You're not your fucking khakis. You're the all-singing, all-dancing crap of the world. - Tyler Durden (Fight Club) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
