[jira] [Updated] (TUSCANY-3906) Enhancement to ThreadMessageContext enabling external tooling to retrieve the previous message context in a given invocation chain.

["Eric Larsen (JIRA)" <de...@tuscany.apache.org>]

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

Eric Larsen updated TUSCANY-3906:
---------------------------------

    Attachment: core-spi-ThreadMessageContext.patch

> Enhancement to ThreadMessageContext enabling external tooling to retrieve the previous message context in a given invocation chain.
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-3906
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3906
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: SCA Java Runtime
>    Affects Versions: Java-SCA-2.x
>            Reporter: Eric Larsen
>             Fix For: Java-SCA-2.x
>
>         Attachments: core-spi-ThreadMessageContext.patch
>
>
> PREVIOUS_CONTEXT has been added to the ThreadMessageContext in core-spi.  At any given time in a thread, PREVIOUS_CONTEXT represents it's immediate previous (old) message context in the thread.  This is added strictly for the use of monitoring or other tooling, enabling the retrieval of the correct component name in case getService() returns a proxy.  PREVIOUS_CONTEXT doesn't have any other meaning or use in the invocation chain other than this external tooling support.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira