[
https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin....
]
Werner Müller commented on RTGOV-645:
-------------------------------------
When testing the community edition
http://downloads.jboss.org/overlord/tmp/overlord-rtgov-2.0.2-SNAPSHOT.zip, we found the
following issues:
- A Situation is always resubmitted to localhost:8080. Instead, it should be resubmitted
to the original target address of the request.
- Resubmitting a SoapFault (generating the same SoapFault) creates a new root Situation,
instead of a "Resubmit Failure" (child).
(A SoapFault situation in our case is created based on the existence of the
'soap_fault_info' property,
and not because of an Exception in the message.)
- Scenario:
A request is received which triggers a SchemaValidationException. The request has no
Security element.
A failure Situation is created for the Schema Validation error.
The schema error is corrected and the Situation is resubmitted.
A "Required policies missing" Exception is generated for the missing Security
element.
Error: This 2nd Exception is shown as new root Situation, not as a "Resubmit
Failure" (child).
- Scenario:
Several failure Situations are resubmitted with the bulk action.
As there was no change in the message, all of them end with the original failure.
Error:
For each one of those Situations, a new root Situation is displayed instead of a
"Resubmit Failure" (child).
However:
If the Situations are resubmitted individually via the Resubmit button on the
"Message" tab,
the "Resubmit Failure" (child) is properly created.
If one of the Situations resubmitted in bulk already has children,
the new failure Situation is correctly shown as child situation.
- A newly created child situation should have the same Status as its ancestor.
Currently it is created in Status UNRESOLVED.
- A Refresh button is missing on the "Resubmit Failures" tab, as it is available
on the "Situations" page.
- For consistency reasons, the hover text over the bulk "Retry" button should
say "Resubmit".
- The "Resubmit Failures" tab should contain a refresh button, as it is on the
"Situations" page.
- (The following is a a change to the original requirement. It came up because we now have
list views instead of a tree view.)
The columns on the "Resubmit Failures" tab should be sortable, as they are on
the "Situations" page.
The default sort order should be the same as the default sort order on the
"Situations" page
(currently descending by Timestamp).
- The filter criteria on the "Situations" page should be preserved during the
session.
Currently they are cleared when you navigate away from that page.
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)