[
https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin....
]
Gary Brown commented on RTGOV-645:
----------------------------------
Have an implementation of these requirements, albeit not visually represented using a
tree, in this branch:
https://github.com/objectiser/rtgov/tree/RTGOV-645
This can be built locally (using mvn clean install -Pdocs) - the docs profile will be
required initially to build a version of the docs to be included in the distribution. This
distribution is for installation into a Wildfly 8.1 environment (which will also need
switchyard to be installed to create some situations). The distribution will be available
from "distribution/overlord-rtgov-dist-all-wildfly8/target".
The new install instructions for this build are documented here:
http://docs.jboss.org/overlord/rtgov/2.1.0.Beta1/userguide/html/_installa...
(suggest using the ./standalone.sh startup approach shown at the end of section 2.1 to
initialise the SSO mechanism).
Note: these changes are currently made in master, but will be backported to the EAP
version once completed.
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.2.0
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)