You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Nash (JIRA)" <tu...@ws.apache.org> on 2008/02/28 15:01:51 UTC
[jira] Resolved: (TUSCANY-2055)
ServiceReference.getConversationID() not returning generated conversation
IDs
[ https://issues.apache.org/jira/browse/TUSCANY-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Nash resolved TUSCANY-2055.
---------------------------------
Resolution: Invalid
The current implementation is correct. This API returns the conversation ID that was set by ServiceReference.setConversationID() and will be used for the next conversation to be initiated by this service reference. This is not the same as the conversation ID for the current conversation, which is returned by CallableReference.getConversation().getConversationID().
> ServiceReference.getConversationID() not returning generated conversation IDs
> -----------------------------------------------------------------------------
>
> Key: TUSCANY-2055
> URL: https://issues.apache.org/jira/browse/TUSCANY-2055
> Project: Tuscany
> Issue Type: Bug
> Components: Specification
> Affects Versions: Java-SCA-Next
> Reporter: Kevin Williams
>
> ServiceReference.getConversationID() returns null unless the Conversation ID is set by the user.
> This is the current implementaiton:
> public Object getConversationID() {
> return conversationID;
> }
> It seems that that if the cached ID is null, and there is a valid related Converasation object then the impl should return the related Conversation.getConversationID.
--
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org