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

[ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-645: ---------------------------------- I've numbered the responses to help track the individual issues in further comments: (1) "A Situation is always resubmitted to localhost:8080. Instead, it should be resubmitted to the original target address of the request." Can you create a separate jira for this. The problem is that currently this information is not captured - will need to consult the switchyard team to see what is possible, (2) "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.)" Does the EPN that creates the situation add the properties from the request into the situation? (See the sample ordermgmt/epn) (3) "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)." The security issue may need to be investigated by the switchyard team - could you create a separate jira for this and if possible attach the swyd app (or atleast the switchyard.xml). Can you also attach the epn that creates the situation. (4) Bulk vs individual resubmit - found this problem after further testing and has now been fixed. (5) "A newly created child situation should have the same Status as its ancestor. Currently it is created in Status UNRESOLVED." This should be working - can you try the ordermgmt sample, submitting "mvn exec:java -Dreq=order5bad", which should result in a schema error being reported as exception, change the situation status (and assign), and then resubmit, letting me know whether the resulting child situation is UNRESOLVED or not? If it is not UNRESOLVED, then we need to examine what the differences are between your app and the sample. (6)/(8)/(9) - Can you create a jira for this. (7) - tooltip text change shouldn't be a problem (10) - persistence filter - can you create a separate jira for this as well please. -- This message was sent by Atlassian JIRA (v6.3.11#6341)