I was hoping from the title of this JIRA that the proposal was to persist the implementation instances in the Http Session object not just the conversationId. The ConversationScopeContainer would know how to store/retrieve from an HttpSession object associated with the conversationId. This would allow for exploiting existing infrastructure for failover and session affinity.
On 6/27/07, Mike Edwards (JIRA) <tuscany-dev@ws.apache.org> wrote:
[ https://issues.apache.org/jira/browse/TUSCANY-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508486] Mike Edwards commented on TUSCANY-1377: --------------------------------------- There is a mixture of 2 things here, as described in Sebastien's last comment: 1) Handling of Scope for components (he mentions implementation.java, which is fine) 2) Dealing with conversational sessions on the HTTP binding These two are NOT directly related. You can do one without the other. I'd suggest sorting out the HTTP binding first - only once there is a conversation going on between 2 components over the wire does it become useful to implement the Scope attribute on a component. > 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]
