Here is some code we use. Basically it uses commons pooling and creates a pool of stubs. The expensive operation of creating the axis2 configuration etc is only done once. It would be simple to wrap it as a proxy of your stub interface and put the attached code in the proxy and so the implementation details hidden from the caller. Hope it helps. P
_____ From: hakon.sageh...@googlemail.com [mailto:hakon.sageh...@googlemail.com] On Behalf Of Håkon Sagehaug Sent: 09 October 2009 12:02 To: axis-user@ws.apache.org Subject: Increase performance using axis 2 client stubs hi all, In our project we've got a web portal that uses web services, that we call by generating stubs using axis2 lib, as the back bone. I'm looking for ways to improve the performance in the calling bit now I've stated reusing the HttpClient object that is used, we have a Util class that wrappes the logic of calliing all the services so for now we're interacting with three, and all uses the same HttpClient object. Should every call be inside a syncronized block?like this synchronized(httpClient){ call service } Or is it a better way to do this?Could the http clients be in a pool managed by tomcat in some way? Also if there is any other tricks on how to increase performace on client side axis2 calls, please say how cheers, Håkon -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company)
Axis2ClientWebService1.java
Description: Binary data
