**My previous post got mangled by my email service--Sorry!
Maybe it will be helpful for me to provide a bit more detail. Here is the content of a web services call that doesn't work: POST /imapi HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.1 Host: dev8:6070 Cache-Control: no-cache Pragma: no-cache SOAPAction: "atpws_getCellInfo" Content-Length: 592 <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Body> <userName xmlns="http://imapi.atp.com";></userName> <password xmlns="http://imapi.atp.com";></password> <imname xmlns="http://imapi.atp.com";>pedev8</imname> <bufferType xmlns="http://imapi.atp.com";> BUFFER_MODE_DEFAULT </bufferType> <connectionId xsi:type="xsd:long" xmlns="http://imapi.atp.com";>0</connectionId> </soapenv:Body> </soapenv:Envelope> Here is the content of a call that does work: POST /imapi HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.0 Host: dev8:6070 Cache-Control: no-cache Pragma: no-cache SOAPAction: "atpws_getCellInfo" Content-Length: 727 <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Body> <userName xsi:type="xsd:string" xmlns="http://imapi.atp.com";></userName> <password xsi:type="xsd:string" xmlns="http://imapi.atp.com";></password> <imname xsi:type="xsd:string" xmlns="http://imapi.atp.com";>pedev8</imname> <ns1:bufferType xsi:type="ns1:IMBufferType" xmlns="http://imapi.atp.com"; xmlns:ns1="http://imapi.atp.com";> BUFFER_MODE_DEFAULT </ns1:bufferType> <connectionId xsi:type="xsd:long" xmlns="http://imapi.atp.com";>0</connectionId> </soapenv:Body> </soapenv:Envelope> The only thing that changes on the client side is the version of the Axis-related jars I am using. That is why I was looking for some sort of configuration option that would make Axis 1.1 behave like Axis 1.0. I did take your advice about changing the client-config.xml file. I tried overriding it by specifying an alternate file as well as changing the one that resides in axis.jar. After my changes, the client-config.xml file looks like this: <?xml version="1.0" encoding="UTF-8"?> <deployment name="defaultClientConfig" xmlns="http://xml.apache.org/axis/wsdd/"; xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";> <globalConfiguration> <parameter name="sendXsiTypes" value="true"/> </globalConfiguration> <transport name="http" pivot="java:org.apache.axis.transport.http.HTTPSender"/> <transport name="local" pivot="java:org.apache.axis.transport.local.LocalSender"/> <transport name="java" pivot="java:org.apache.axis.transport.java.JavaSender"/> </deployment> None of these changes has produced the desired result. I am starting to wonder if I am even in the ballpark. I will continue digging but would certainly appreciate any help you can offer. To answer Anand's question about this being server or client code - my code is part of a server product but is acting as a client to another product via it's web services interface. As I mentioned before, the Axis 1.1 jars are already on the classpath. My understanding is that there is no longer a separate axis-client.jar file. The axis.jar file has both a client-config.xml and server-config.xml inside of it. Much Thanks, Tony _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web!
