[
https://issues.jboss.org/browse/RTGOV-181?page=com.atlassian.jira.plugin....
]
Gary Brown commented on RTGOV-181:
----------------------------------
As part of this issue, maybe change Context.Type.Message enum to Context.Type.Exchange -
so that rather than being SOA message send/receive specific, it could relate to any
exchange of information between two activities - so would also be relevant to scheduling
and executing a job.
Associating separate Activity Units with SOA and BPM related events
-------------------------------------------------------------------
Key: RTGOV-181
URL:
https://issues.jboss.org/browse/RTGOV-181
Project: RTGov (Run Time Governance)
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M5
Due to the way activity collector implicitly associates activity events based on threads,
the SOA related (interaction) events are stored on one activity unit, while the BPM (e.g.
BPEL) related events generated by the process executing within the service, are stored in
a separate activity unit(s).
We need a way in which to associate these activity units, to reflect the relationship
between the activities.
One possible solution is to register an activity when a BPM related job is added to a job
queue, and then similarly when it is retrieved. This may require a change to the riftsaw
engine to generate this type of event.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira