axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Davanum Srinivas <dava...@gmail.com>
Subject Re: [Axis2] MTOM Support
Date Wed, 24 Aug 2005 12:49:20 GMT
Please open a jira bug to track the issue.

thanks,
dims

On 8/24/05, Saminda Abeyruwan <saminda@opensource.lk> wrote:
> Hi all,
> 
> As Thilina wrote current code deals MTOMized message with "chunking" as
> default. It's good, but the problem is flexibility. AFAIK HttpClient can
> set the "Content-Length" properly via RequestEntity. I inquire
> httpclinet-dev list the capability of it and they are pretty good about
> it. If we can decide to give this flexibility of supporting "chunking"
> on/off, it would be great.
> 
> Saminda
> 
> Thilina Gunarathne wrote:
> 
> > Hi,
> > See my comments below....
> >
> >     I'd like to see something like this.
> >
> >     If(doingMTOM){
> >         // by default chunking is on
> >     }else{
> >         // by default chunking is off
> >     }
> >
> >
> > Yes.. this is exactly what is happening now. If we are sending an
> > MTOMized message chunking is by switched on. It was reported that
> > HTTPClient reports a wrong content-length. This was the reason behind
> > that move....
> >
> > But the problem Shaminda talks is some interop endpoints (eg :
> > Whitemesa MTOM endpoint) does not support http chunking. So he wants
> > to know whether we can give the option of enabling and disabling
> > chunking for MTOM....
> >
> >     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);
> >
> >
> > Yes.. This should be.... But what Shaminda wants is,
> >     mepClient.doMTOM(boolean);
> >     mepClient.doChunking(boolean); // even in the MTOM case
> >
> > Thanx & Regards,
> > ~Thilina
> >
> >
> >     -- 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
> >     >
> >     >
> >
> >
> >
> >
> > --
> > "May the SourcE be with u"
> > http://www.bloglines.com/blog/thilina              http://webservices.apache.org/~thilina/
> > <http://webservices.apache.org/%7Ethilina/>
> 
> 
> 


-- 
Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform

Mime
View raw message