On Tue, 2006-10-17 at 10:24 +0530, Chamikara Jayalath wrote: > Hi All, > > Currently according to the way ServiceClient.cleanup() method hs been > written, it seems to be stopping the listner only if the > ConfigurationContext was not passed by the the user. So if the > ConfigurationContext was passed by the user he has to write > his code as follows > > <code> > > ConfigurationContext configContext = > ConfigurationContextFactory.createConfigurationContextFromFileSystem(); > ServiceClient serviceClient = new ServiceClient > (configContext,null); > //Do the invocation > configContext.getListenerManager().stop(); > serviceClient.cleanup(); > > </code> > > If line 4 was not included to stop the listner, the client hangs. > Is this the expected behaviour, or should we do a change in the > 'cleanup' method to stop the listner in all the scenarios ?
Hmmm. The problem is that there can be many servic clients running off the same config context - as such you can't clean the world when a single service client is done. I think your lines 4 & 5 should be in the other order .. you clean up the service client and then tell configcontext to stop the world. Not sure I see a sane way around this. Sanjiva. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
