Hi Michele, You can store the state information as properties of the context hierarchy where appropriate.
To make state available across different client invocations you have two options: 1.) If it is the same client's requests that you want to maintain state you can place the state attributes in service context or service group context as required by making the service available application scope. 2.) If you want to share state across different clients then you will have to place state attributes in the configuration context. In this case make sure you give unique identifiers as keys. Thanks, Ruchith On 6/1/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
Hi all, how can I maintain the service state across different client invocations (other than through static fields)? Thanks in advance, Michele --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
