Hi Deepal, i'm not sure i completely understand your question, but let me try :-)
The ServiceManager forwards messages, send from a client, to the LocalMonitor and sends the response back to the client. The Client, ServiceManager and LocalMonitor must not necessarily run on the same machine but in a LAN. The goal is to recognize the limits of Axis2 (and also of Axis1) with certain configurations (signing, encryption or both for example). The ServiceManager uses a stub for the LocalMonitor to forward the client-messages. With your hints the stub has been refactored to a class-field and will be instantiated when the first invocations comes from a client. Additionally the scope of the ServiceManager has been set to "application". So i think the Web Service ServiceManager uses the same ServiceClient for all service invocations of the client. But there is no way, that the ServiceManager and the Client uses the same ServiceClient-instantiation. Hopes, this is the answer you asked for. Otherwise tell me. Bye Falk Deepal Jayasinghe wrote: > Hi Falk; > Is there any possibility of creating one service client and use that for > all the service invocations. > > Thanks > Deepal > > Falk Bauer wrote: > > >>>>> Well you can have this behavior in the client side , ... >>>>> >>>>> >>>>> >> That was it. My code produces new ServiceClients at server-side and so the >> deployment happens in every new call of the client. >> >> Some more explanations: >> >> The Round-Trip-Time Tests send a message the following way: >> Client->ServiceManager->LocalMonitor->ServiceManager->Client >> >> So in the ServiceManagerSkeleton-class there is an instantiation of a stub >> for the LocalMonitor. Here were two issues responsible for the repeated >> deployment: >> >> 1. The stub was instantiated in a method-local object. So the deployment >> happens each time of the instantiation of the stub. >> Refactoring this method-local object to a class-field corrects this point. >> >> 2. I have forgotten the attribute scope="application" for some services.xml. >> >> >> So the SimpleHTTPServer works absolutely right. It was solely my fault. >> >> Many many thanks to both of you. Your mails were greatly helpfull! >> By the way, the round-trip-times alleviates from 700ms to 20ms ;-) >> >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
