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

Werner Müller (JIRA) issues at jboss.org
Wed Apr 8 12:28:19 EDT 2015


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

Werner Müller commented on RTGOV-645:
-------------------------------------

I did some investigations with the answer of (3). Thanks for reaching out to the forum. At the moment, it seems to me, as this would be the solution. But I still want to continue the investigations tomorrow. (There are some tricky constructs in our code.) Therefore, I don't want to give my final ok.

If this and (7) is solved, I agree with your understanding.

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



More information about the overlord-issues mailing list