The lifetime of the service instance depends on ur service scope. The default scope is 'Request scope' causing a service instance to be created per each request. In your case the service scope hs to be changed to 'application' causing a single service instance to be present for the whole lifetime of the Axis2 system.
To change the scope edit your services.xml file as follows.
<service name="Service1" scope="application">
</service>
More info. can be found in following article by Deepal,
http://www.developer.com/services/article.php/3620661
Chamikara
On 10/1/06,
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi there,
I have a question/remark about the working of the InOrder QOS for Sandesha2. I am working on a scenario where I want to sent multiple message in one sequence with the InOrder QOS enabled. This is working, but what I am missing currently is that I would like the same instance of the service being called for the whole sequence. I need this because the messages send in the sequence at the end of the sequence have to be consolidated in a single response based on the content of all the messages in the sequence.
I found that currently the messages in the sequence are processed individually by seperate service instances.
What do you think of this?
Thanks,
Tijs
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
