[
https://issues.apache.org/jira/browse/TUSCANY-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507963
]
Jean-Sebastien Delfino commented on TUSCANY-1377:
-------------------------------------------------
Here's how I see this working:
- Support the conversational annotations in implementation-java, when a
business method is invoked on a conversational interface, generate a new
conversation unique id, when a method with @EndConversation is invoked reset
the conversation id
- Carry the conversation id through service invocations in the conversationID
field of the SCA Message
- Support @Scope("CONVERSATION") in implementation-java, associate a Java
component implementation instance with a conversationID and dispatch calls to
the instance associated with an incoming conversation id.
- Add support for conversation ids to the WS binding, store the conversation ID
found in the SCA message in the HTTP session used to communicate with a Web
Service or Web Service client.
- Other bindings may propapate conversation IDs in a different and binding
specific way, but that's out of the scope of this particular JIRA.
> Conversational PM- HTTP Session persistence
> -------------------------------------------
>
> Key: TUSCANY-1377
> URL: https://issues.apache.org/jira/browse/TUSCANY-1377
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-Next
> Reporter: ant elder
> Fix For: Java-SCA-Next
>
>
> Implement conversational PM- HTTP Session persistence
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
