The @jws:conversation annotation specifies the role that an individual method or callback plays in a service's conversations. Note that these roles are different between methods and callbacks.
Note: The Web Service control uses the @jc:conversation annotation instead of the @jws:conversation annotation. The functionality is the same.
@jws:conversation
phase="none" | "start" | "continue" | "finish"
One of four values indicating the method or callback's role in conversations. Note that only continue and finish are available for callbacks, because a callback is necessarily part of a conversation, although it cannot start a conversation.
The @jws:conversation annotation sets the conversation phase attribute for a method or callback to specify its role in the service's conversations.
The following rules apply to this annotation's use:
Possible attribute values are as follows:
Set the phase attribute to continue for any method or callback that is likely to be used for communication with a client in connection with an ongoing request. In particular, these are methods that are clearly intended to be called subsequent to the conversation's start and before its finish. These include requests for or responses with additional information, requests for progress or status, and so on.
It is also possible to finish a conversation by calling the JwsContext interface finishConversation method. For more information, see Managing Conversation Lifetime.
The phase attributes default values are as follows: