[
https://issues.apache.org/jira/browse/TUSCANY-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws resolved TUSCANY-2056.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: Java-SCA-Next)
Java-SCA-1.2
The problem was that the callable reference was serializing the wrong
conversationId to the output XML when being passed over a web service binding.
It was using the conversationId field that is used to hold the values that
users can set rather than the conversationId field relating to the currently
active conversation. I've put a fix in trunk and also added the test case you
contributed to itest/callablereference-ws . Thank you very much for that.
> Conversation does not continue if a Service Reference is passed as a return
> value (not as a parameter) when using binding.ws
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-2056
> URL: https://issues.apache.org/jira/browse/TUSCANY-2056
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-1.1
> Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk
> 1.5.0_10
> Reporter: Daniel Stucky
> Assignee: Simon Laws
> Fix For: Java-SCA-1.2
>
> Attachments: test.zip, test.zip
>
>
> This problem is related to TUSCANY-2028. It is exactly the same use case, but
> instead of the default binding (sca) I now use binding.ws.
> And as in Tuscany 1.0.1 with binding.sca the Conversation is not reused. So I
> guess the fix that went into Tuscany 1.1 did only affect binding.sca and not
> binding.ws.
--
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]
