Never mind. A colleague already had figured a solution that allows to
take advantage of reusing the same HTTP connection but only on a per
instance of the service basis.
Options options = service._getServiceClient().getOptions();
HttpTransportProperties.Authenticato
I think I am seeing the same behaviour reported by Dobri Kitipov on
the thread started on Aug 14, 2009.
At the end of that thread, Dobri says:
"In fact the question of Amila is one that I am really interested in.
I have a similar scenario over here. We have a use case when different
clients are cr
Hi
I am using Axis2 for my web services client to run an automated
test of my server.
We were using Axis2 1.4.1 and recently we decided to use Axis2 1.5.1
Our web service has a feature that allows to restrict how many
simultaneous requests are made by the same customer, resulting in a
SOA
