The part that I can see as the problem is the last one where the request is written to the wire. I can't understand how the content type became application/x-www-form-urlencoded (should have been text/xml for soap1.1. Since I see the SOAPAction header I suppose its 1.1). Is there any other configuration regarding the httpclient ? (that may have changed its behavior)
Ajith On Fri, May 30, 2008 at 8:01 AM, Aljen7 <[EMAIL PROTECTED]> wrote: > > I can see thanks to dubugging that the soapEnvelope in request is > constructed in Stub class correctly and it remains unchainged during axis2 > engine which ended in the correct request calling messageContext is OK > (afaik). Then why is it changed (empty - no body) when it comes to server. > > > > -- > View this message in context: > http://www.nabble.com/Axis2-%28ADB%29-%3A-Problem-with-empty-RequestBody-tp17532435p17557256.html > Sent from the Axis - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Ajith Ranabahu Reading, after a certain age, diverts the mind too much from its creative pursuits. Any man who reads too much and uses his own brain too little falls into lazy habits of thinking - Albert Einstein --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
