[overlord-issues] [JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back

[Gary Brown (JIRA)]

    [ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057040#comment-13057040 ] 

Gary Brown commented on RTGOV-645:
----------------------------------

>From the forum thread for issue (3), it appears that currently the only solution is to provide a context mapper on the JMS binding, to map the RTGov property to the JMS message and then back again, within the second service.

Therefore once the minor issue (7) has been fixed, I believe all other further work is now associated with the other jiras. Can you confirm this is your understanding as well?




> Resubmitted message should identify source situation to enable further failures (situations) to be linked back
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: RTGOV-645
>                 URL: https://issues.jboss.org/browse/RTGOV-645
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.1.0.Beta2
>
>
> When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events.
> If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)