Hi Thilina, yes with tcpmon everything looks fine by looking at the HTTP requests (binary data + xop include reference) , it's actually logical to have the SOAP request constructed before SOAPMonitor is invoked.
Regards, Angel On 1/15/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
Hi Angel, Hope you have a OMText with optimised set to "true" in the above case. Are you using any databinding mechanisms.. I'm not sure whether it is an issue with SOAPMonitor... Can you please try sniffing the message with tcpmon[1]. Thanks, Thilina [1] http://ws.apache.org/commons/tcpmon/ On 1/14/07, Angel Todorov <[EMAIL PROTECTED]> wrote: > Hi all, > > I am doing a test of MTOM - sending a binary file and then saving it > somewhere on the server. I follow the MTOM guide for Axis2. I am using > the SOAP Monitor applet in order to investigate the SOAP requests and > responses, and in both cases where MTOM is enabled and disabled on the > client side, the SOAP request 's contents is the same, more > specifically : > > <ns2:binaryData xmlns:ns0="http://www.w3c.org/2005/05/xmlmime"; > ns0:contentType="application/octet-stream"> (binary sting here ) > </ns2:binaryData> > > the contents of the binary string is also the same. Can anyone provide > some clarification ? Thanks > > Regards, > Angel > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thilina Gunarathne WSO2, Inc.; http://www.wso2.com/ Home page: http://webservices.apache.org/~thilina/ Blog: http://thilinag.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
