The mtom guide databinding section was one of the last things to get tested
... the adb section should be working but the code / documentation freeze
happened before xmlbeans / mtom got tested, and I suspect there is some work
needed to be done as issue AXIS2-1031 suggests.

You could help us with it or try mtom with adb.

Robert

On 11/16/06, Mariusz Woloncewicz <[EMAIL PROTECTED]> wrote:

I ran sample code from http://ws.apache.org/axis2/1_1/mtom-guide.html#252
but a soap message sent to server was as following:

   <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
      <soapenv:Header />
      <soapenv:Body>
         <sendData xmlns="http://myMtomNS/types";>
            <MyBinaryData>dGVzdG93eSB0ZWtzdA==</MyBinaryData>
         </sendData>
      </soapenv:Body>
   </soapenv:Envelope

I tried to enable MTOM optimization at client side:

stub._getServiceClient().getOptions().setProperty(
Constants.Configuration.ENABLE_MTOM, Constants.VALUE_TRUE);

but it didnt help.
Sample with ADB databinding works fine (instead of binary data there is
<xop:Include> reference to mime attachment)

Has the MTOM/XMLBeans databinding already been implemented (jira:
AXIS2-1031)?

Thanks,
Mariusz Woloncewicz


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to