I wrote my sample code with Axis2 and deployed Axis2.war on both jakarta tomcat 4.1.31 and IBM WebSphere 6.0.2. I found it behaves weird on WebSphere when I was running my Microsoft WSE 3.0 client against it. I enabled MTOM in axis2.xml. From WSE 3.0 client to axis2.war on tomcat, the content type of HTTP response is always xop+xml/multi-part so that WSE 3.0 client can happilly recoganize it. But from WSE 3.0 client to axis2.war on WebSphere, some times the content type in response is xml/text so that WSE 3.0 client rejects to accept it. If I did something, like restart WebSphere or re-compile the C# client, the axis2.war on WebSphere will return xop+xml/multi-part content type. It's very irregular. Does any have the same experience or any idea? I think WebSphere web container temper the HTTP headers but I don't know why it doesn it.
It's kind of urgent. Thanks for help. sctt
