Hello again Jeff!
That did the trick. The configuration I was trying to set on the Call object
directly before was incorrect and was causing the multiple requests and the
incorrect transport of the actual call.
I appreciate the help with this, and thanks to Shadab as well!
Mario-
----- Original Message ----
From: "Walker, Jeff" <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Monday, October 8, 2007 11:27:23 AM
Subject: RE: Axis 1.4 configuration to use HTTP/1.1
DIV {
MARGIN:0px;}
Hi Mario,
Shadab got his problem solved. (He
wanted to use HTTP 1.1 in Axis 1.4 and do it programmmatically on the
clientside). the solution he emailed to me
is:
Hi Jeff,
Thank you so much for all the
info..
I have succesfully implemented the second
alternative of using - CommonsHTTPSender as the Transport Sender of the axis
client, viz.,
BasicClientConfig basicClientConfig =
new BasicClientConfig();
SimpleChain simpleChain = new
SimpleChain();
simpleChain.addHandler(new
CommonsHTTPSender());
basicClientConfig.deployTransport("http",
simpleChain);
LogonService_Service logonService =
new
LogonService_ServiceLocator(basicClientConfig);
and in the server-config.wsdd I added
the
pivot="java:org.apache.axis.transport.http.CommonsHTTPSender"
Cheers,
Shadab
But your issue is the three requests,
where one is in http 1.0 and the other two are http 1.1.
Correct?
If so, I still
think you are registering two handlers (that use CommonsSender and hence
http 1.1) and the default HTTPSender is
called in the middle to send it using HTTP 1.0.
If that is also true, then the programmatic registering of the two handlers is
incorrect.
-jeff
From: Mario Felarca
[mailto:[EMAIL PROTECTED]
Sent: Monday, October 08, 2007 11:56
AM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.4
configuration to use HTTP/1.1
Hello
Shadab!
Sorry I was not able to reply to this until now. I was trying
to set the configuration of the client-side transport to utilize
CommonsHTTPSender via settings on the Call object. That was not working. Jeff
had given me some alternatives to try, such as setting the properties on the
client-side EngineConfiguration. Unfortunately, I have not had the chance to
try that yet as another project took precedence. Hopefully I can try that out
later today or tomorrow and get back to the list with my results.
Were
you able to make some progress on this front in a different
direction?
Thanks!
Mario-
-----
Original Message ----
From: Shadab <[EMAIL PROTECTED]>
To:
axis-user@ws.apache.org
Sent: Wednesday, October 3, 2007 2:36:50
AM
Subject: Axis 1.4 configuration to use HTTP/1.1
Hi All,
Please let me know if there is any way to configure
Axis1.4 such that it
uses HTTP/1.1 instead of HTTP/1.0
The request
from the soapclient (implemented using service stub) lands with
Axis/1.4
which in turn by default presumably uses HTTP/1.0.
Can't this be
changed somehow using CommonsHTTPSender as pointed by mail
thread of
Mario/Jeff "Axis 1.4 CommonsHTTPSender question" Date
Sep:20:2007
?
Mario/Jeff,
Please let me know if you people have
reached some solution and will that
solution be helpful in the scenario I
have told above...
Thanks,
Shadab
--
View this message in
context:
http://www.nabble.com/Axis-1.4-configuration-to-use-HTTP-1.1-tf4560281.html#a13014221
Sent
from the Axis - User mailing list archive at
Nabble.com.
---------------------------------------------------------------------
To
unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
commands, e-mail:
[EMAIL PROTECTED]
