I guess Saminda is stating the same thing, A similar piece of code should be in the sender right now. my guess is we'll put an entry in the axis2.xml (the configuration) stating which setting is to be used as default.

On 8/23/05, ERAN CHINTHAKA <[EMAIL PROTECTED]> wrote:
I'd like to see something like this.

If(doingMTOM){
    // by default chunking is on
}else{
    // by default chunking is off
}


But, this should be configurable through the MEPClient api. Meaning, one
should be able to explicitly override the default settings through the
MEPClient API.

something like, mepClient.doMTOM(boolean);

-- Chinthaka

Saminda Abeyruwan wrote:

> Hi all,
>
> Studing the current code for MTOM support for Axis2, it's being found,
> when "optimized" is on, CommonsHttpTrasnsportSender uses "chunk" as
> default. When doing interop tests, i've found that some interop end
> points couldn't handle "chunked" stream. Could we allow "chunking"
> on/off via Axis2.xml, till the policy is integrated to the system.
>
> Any thoughts...
>
> Saminda
>
>



--
Ajith Ranabahu

Reply via email to