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 2007/09/05 01:14:44 UTC

[jira] Updated: (TUSCANY-1661) Conversation ID not set in CallableReference by RequestContextImpl

     [ https://issues.apache.org/jira/browse/TUSCANY-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Nash updated TUSCANY-1661:
--------------------------------

    Attachment: jira1661

Add code to RequestContextImpl and CallableReferenceImpl to set the conversation ID from the ThreadMessageContext into the returned CallableReference.

> Conversation ID not set in CallableReference by RequestContextImpl
> ------------------------------------------------------------------
>
>                 Key: TUSCANY-1661
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1661
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Core Runtime
>    Affects Versions: Java-SCA-Next
>         Environment: Windows XP
>            Reporter: Simon Nash
>             Fix For: Java-SCA-1.0
>
>         Attachments: jira1661
>
>
> The RequestContext.getServiceReference() and RequestContext.getCallbackReference() methods don't set the conversation ID into the returned CallableReference.

-- 
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