I belive this should be done with, property TRANSPORT_CONSTANTS that has a value HashMap in the message context. The transport sender would write the headers given in the HashMap as the tranport headers.
I would try to change the code to take care of this Thanks Srinath On 5/28/05, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: > resending with [Axis2] > > ---------- Forwarded message ---------- > From: Thilina Gunarathne <[EMAIL PROTECTED]> > Date: May 27, 2005 12:08 PM > Subject: Setting the content type of the meesage > To: [email protected] > > Hi all, > Current MTOM implementation works on OM level. An mtom optimised MIME > message should have a content-type http header to saying that > "multipart/related". We need a way to inform the transport sender that this > is a optimised message, so that it should put the content type header as > xop. but currently it seems no way of conveying that piece of information > from MTOM writer to transport sender. > Since MTOM works in OM level it cannot access the Message context. Any idea > to get this through. > > Thanks & regards, > ~Thilina > > -- Lanka Software Foundation -- > > "May the SourcE be with u" > > -- > > -- Lanka Software Foundation -- > > "May the SourcE be with u"
