[
https://issues.jboss.org/browse/BAM-111?page=com.atlassian.jira.plugin.sy...
]
Gary Brown commented on BAM-111:
--------------------------------
Some of this capability is provided with the call trace graph, which shows the trace of a
business transaction instance as a tree structure.
This issue is looking to provide a graphical diagram to show the relationship between the
tasks. It would be useful, but is not urgent for the first version - firstly we should
make sure the correlation across components, and the representation as a call trace, work
well.
Graphical representation of the current status of a conversation
instance
-------------------------------------------------------------------------
Key: BAM-111
URL:
https://issues.jboss.org/browse/BAM-111
Project: Business Activity Monitoring
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M4
Attachments: CommsDiagStyle.gliffy, CommsDiagStyle.png, FlowDiagStyle.gliffy,
FlowDiagStyle.png
Initially the Savara web console will display a conversation instance as a table of
activity events.
This task will provide a graphical status view of the conversation instance, showing the
execution path taken, and if still active, where the instance is currently in its
execution.
Although BPMN2 is the principle choreography representation that will be used, not all
choreographies will be defined with a BPMN2 choreography - so we need to consider how this
graphical representation will be defined.
One approach may be to derive a BPMN2 like representation, based on the global Scribble
protocol definition, as this will be the canonical representation used for all
conversations being monitored. It would also be simpler than the BPMN2 original - just
depends whether users would expect to see if based on the original representation.
The other approach would be to only support graphical representation where a BPMN2
choreography has been defined, and provide a faithful graphical representation of the
original choreography.
To be decided ....
However the same approach could be used as with RiftSaw - generate SVG images as
snapshots of the state, and if the state changes while displaying, then just generate a
new image.
--
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