[
https://issues.apache.org/jira/browse/TUSCANY-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Nash reassigned TUSCANY-2299:
-----------------------------------
Assignee: Simon Nash
> Client-set callback id not preserved on stateless callback
> ----------------------------------------------------------
>
> Key: TUSCANY-2299
> URL: https://issues.apache.org/jira/browse/TUSCANY-2299
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-Next
> Reporter: Kevin Williams
> Assignee: Simon Nash
>
> The Java CAA spec says the following re: stateless callbacks:
> 613 A stateless callback interface is a callback whose interface is not
> marked as conversational. Unlike
> 614 stateless services, the client of that uses stateless callbacks will not
> have callback methods routed to an
> 615 instance of the client that contains any state that is relevant to the
> conversation. As such, it is the
> 616 responsibility of such a client to perform any persistent state
> management itself. The only information that
> 617 the client has to work with (other than the parameters of the callback
> method) is a callback ID object that is
> 618 passed with requests to the service and is guaranteed to be returned with
> any callback.
> 619 The following is a repeat of the client code fragment above, but with the
> assumption that in this case the
> 620 MyServiceCallback is stateless. The client in this case needs to set the
> callback ID before invoking the
> 621 service and then needs to get the callback ID when the response is
> received.
> The test:
> org.apache.tuscany.sca.vtest.javaapi.conversation.callback.CallbackTestCase.statelessCallback2
> demonstrates this issue and is currently @Ignore(d)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
