overlord-issues March 2011

overlord-issues@lists.jboss.org

15 discussions

[JBoss JIRA] Created: (SOAG-104) Service activity console

by Gary Brown (JIRA)

Service activity console ------------------------ Key: SOAG-104 URL: https://jira.jboss.org/jira/browse/SOAG-104 Project: SOA Governance Issue Type: Task Security Level: Public (Everyone can see) Components: Behavioural Monitoring Affects Versions: 1.0 MR3 Reporter: Gary Brown Assignee: Jeff Yu Fix For: 1.0 MR3 Console for providing access to service activity information. User needs to be able to view service activity information in various ways, including: 1) Raw service events - although this view should only generally be used for detailed analysis 2) Conversation view - using correlation information to group service related events based on a business transaction 3) Conversation per Service vew - correlation information used to group service activity information for a selected service based on a business transaction. Selecting a business transaction to view could be based on time range, based on correlation attribute values, or possibly other custom properties. The console (or governance repository) should enable tokens/locators to be defined against message schema, which can be used to extract business relevant information from the business messages, and used by the console to query appropriate correlated business transactions. If the console is going to provide access to service activity information generated by a variety of different runtime platforms, where different design/modelling approaches have been used, it would be good to enable either the local model (service) or global model (conversation/choreography) views to be represented in a range of appropriate graphical notations - and eventually enable the service activity trace to be replayed back through the graphical representation. Other future requirements may enable business specific views to build on the base information - but this may be through a pluggable views in something like JBoss Workspace. The range of events that may be displayed, and their format, will be defined as a separate task - but the console should be flexible enough to cater for customisaton/extension of the event model. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (SOAG-66) Represent the CDL Exception Handling concept with the 'conversation aware' ESB actions

by Gary Brown (JIRA)

Represent the CDL Exception Handling concept with the 'conversation aware' ESB actions -------------------------------------------------------------------------------------- Key: SOAG-66 URL: https://jira.jboss.org/jira/browse/SOAG-66 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Jeff Yu Currently the Exception Handling mechanism in CDL is not supported in the conversation aware ESB actions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (SOAG-88) Add UML interaction diagrams to SamplesGuide

by Mark Little (JIRA)

Add UML interaction diagrams to SamplesGuide -------------------------------------------- Key: SOAG-88 URL: https://jira.jboss.org/jira/browse/SOAG-88 Project: SOA Governance Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Examples Affects Versions: 1.0 MR1 Reporter: Mark Little Assignee: Jeff Yu Fix For: 1.0 MR2 We need to have a step-by-step worked example that illustrates the use of Process Governance from a developer's perspective. Some of the example text in the SamplesGuide is close to that, but not exactly the same thing. The addition of more text and interaction diagrams would help here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (SOAG-102) Roapmap links on Overlord main page are broken

by Gary Brown (JIRA)

Roapmap links on Overlord main page are broken ---------------------------------------------- Key: SOAG-102 URL: https://jira.jboss.org/jira/browse/SOAG-102 Project: SOA Governance Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Site Reporter: Gary Brown Assignee: Mark Little The 'roadmap' and 'now available' links in the Project Status section appear to be broken. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (SOAG-65) Blocking/waiting behaviour for WhenAction

by Gary Brown (JIRA)

Blocking/waiting behaviour for WhenAction ----------------------------------------- Key: SOAG-65 URL: https://jira.jboss.org/jira/browse/SOAG-65 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Conversation Runtime Reporter: Gary Brown Assignee: Jeff Yu Currently the WhenAction does immediate evaluation of an expression. This construct needs to enable blocking/waiting behaviour if the expression evaluates to false - using the services of an external mechanism that can monitor an expression, and re-evaluate it whenever a change occurs to the state for the session, and then trigger the appropriate service descriptor once the expression does evaluate to true. The expression could also represent a timeout, and therefore this mechanism could be combined with the issue related to the WhenAction handling timeouts (SOAG-33). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

← Newer
1
2
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues March 2011