[
https://issues.apache.org/jira/browse/TUSCANY-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws resolved TUSCANY-1590.
---------------------------------
Resolution: Fixed
The conversational scope container now allows component instances to be
registered against more than one coversation id. So there is no need now to
share conversation ids between reference in the case of stateful callacks.
> Conversation ID's are not unique with multiple references in same component
> ----------------------------------------------------------------------------
>
> Key: TUSCANY-1590
> URL: https://issues.apache.org/jira/browse/TUSCANY-1590
> Project: Tuscany
> Issue Type: Bug
> Reporter: Lou Amodeo
> Assignee: Simon Laws
> Fix For: Java-SCA-1.0
>
>
> I am seeing that the generated conversationId's are not unique when there ar
> 2 (>1) component references. Given the following SCDL both references get
> the same ID assigned.
> <component name="FrontEndConversationalService">
> <implementation.java
> class="test.sca.bindings.ws.components.FrontEndConversationImpl"/>
> <reference name="aBackEndConversationalServiceRef">
> <binding.ws
> wsdlElement="http://components.ws.bindings.sca.test#wsdl.port(BackEndConversationalService/BackEndConversationalServiceSOAP11port)"/>
> </reference>
> <reference name="aBackEndConversationalServiceRef2">
> <binding.ws
> wsdlElement="http://components.ws.bindings.sca.test#wsdl.port(BackEndConversationalService/BackEndConversationalServiceSOAP11port)"/>
> </reference>
> </component>
>
--
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]
