Ah...to clarify my original post. Either I was a little too enthusiastic in 
editing the tcpmon data for brevity or it somehow got stripped out. Here is 
what I really meant to post with the more meaningful SOAP content.



Thanks again!



Mario-





Before changing to use CommonsHTTPSender:



POST /axis/services/USERSERVICE HTTP/1.0

Content-Type: text/xml; charset=utf-8

Accept: application/soap+xml, application/dime, multipart/related, text/*

User-Agent: Axis/1.4

Host: 127.0.0.1:8888

Cache-Control: no-cache

Pragma: no-cache

SOAPAction: ""

Content-Length: 1088



<?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><processMessage
 xmlns="urn:RG"><in0 
xsi:type="xsd:string"><![CDATA[SOMEUSERDATA]]></in0></processMessage></soapenv:Body></soapenv:Envelope>

And now using CommonsHTTPSender:

POST /axis/services/USERSERVICE HTTP/1.1
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
User-Agent: Axis/1.4
Host: 127.0.0.1:8888
Transfer-Encoding: chunked

4c5
<?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><processMessage
 xmlns="urn:RG"><in0 soapenc:arrayType="xsd:anyType[1]" 
xsi:type="soapenc:Array" 
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";><in0 
xsi:type="soapenc:string"><![CDATA[SOMEUSERDATA]]></in0></in0></processMessage></soapenv:Body></soapenv:Envelope>
0
 




----- Original Message ----

From: Mario Felarca <[EMAIL PROTECTED]>

To: [email protected]

Sent: Thursday, September 13, 2007 9:33:31 PM

Subject: Axis 1.4 CommonsHTTPSender question



Hello all!



I have a client where before setting the client to use CommonsHTTPSender, it 
worked fine. The client would post using HTTP 1.0, and it would do so once only 
and everything was fine.



Now, since it is a programmatically defined client, I activate the 
CommonsHTTPSender by adding the following lines to the client:



CommonsHTTPSender reqHandler = new CommonsHTTPSender();

CommonsHTTPSender respHandler = new CommonsHTTPSender();

_call.setClientHandlers(reqHandler, respHandler);



The following line is added to the server-config.wsdd:



 <transport name="http" 
pivot="java:org.apache.axis.transport.http.CommonsHTTPSender" />





The behavior I am seeing in tcpmon when NOT using CommonsHTTPSender is:



POST /axis/services/USERSERVICE HTTP/1.0

Content-Type: text/xml; charset=utf-8

Accept: application/soap+xml, application/dime, multipart/related, text/*

User-Agent: Axis/1.4

Host: 127.0.0.1:8888

Cache-Control: no-cache

Pragma: no-cache

SOAPAction: ""

Content-Length: 1088



<![CDATA[SOMEUSERDATA]]>



The behavior I am seeing in tcpmon when I use CommonsHTTPSender is listed 
below, however it is also notable that it fires three times instead of once, 
all on its own. The first and third time are HTTP 1.1, and the middle one is 
HTTP 1.0. I'm not sure why this behavior exists as well. 



Additionally, there are these strings before and after the soap content, the 
string before is 4c5 and the string after is 0. I don't know where these come 
from either, and if these are the reasons for the 3 seperate calls.



Anyway, the tcpmon is:



POST /axis/services/USERSERVICE HTTP/1.1

Content-Type: text/xml; charset=utf-8

SOAPAction: ""

User-Agent: Axis/1.4

Host: 127.0.0.1:8888

Transfer-Encoding: chunked



4c5

<![CDATA[SOMEUSERDATA]]>

0





Any help or guidance would be greatly appreciated!!



Thanks in advance,



Mario-











---------------------------------------------------------------------

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]

Reply via email to