December 2010 - overlord-issues - Jboss List Archives

[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, 10 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, 10 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, 10 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, 10 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (SOAG-67) Conformance checking for CDL Exception Handling mechanism against 'conversation aware' ESB actions

by Gary Brown (JIRA)

Conformance checking for CDL Exception Handling mechanism against 'conversation aware' ESB actions -------------------------------------------------------------------------------------------------- Key: SOAG-67 URL: https://jira.jboss.org/jira/browse/SOAG-67 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Provide conformance checking between a CDL description with Exception Handling and the equivalent representing in an ESB configuration using '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

14 years

1
2
0 / 0

[JBoss JIRA] Created: (SOAG-97) Have CDL validation deployment lookup Service EPR

by Jeff DeLong (JIRA)

Have CDL validation deployment lookup Service EPR ------------------------------------------------- Key: SOAG-97 URL: https://jira.jboss.org/jira/browse/SOAG-97 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WS-CDL Affects Versions: CONTINUING Reporter: Jeff DeLong Assignee: Mark Little Instead of using annotations in the CDL model to add the ESB EPR to the service/participant for runtime validation purposes, perhaps as part of deployment into the server the deployer could use the service name to lookup the EPR, and then add this information to the validation configuration. This would save the developer from having to copy runtime deployment information into the CDL files. -- 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

14 years

3
3
0 / 0

[JBoss JIRA] Closed: (SOAG-20) Minimise requirement to specify 'session' property on all conversation based service descriptors.

by Gary Brown (JIRA)

[ https://jira.jboss.org/browse/SOAG-20?page=com.atlassian.jira.plugin.syst... ] Gary Brown closed SOAG-20. -------------------------- Resolution: Won't Fix No further work being done on CDL related capabilities in Overlord. This functionality has now been moved to the Savara (www.savara.org) project. > Minimise requirement to specify 'session' property on all conversation based service descriptors. > ------------------------------------------------------------------------------------------------- > > Key: SOAG-20 > URL: https://jira.jboss.org/browse/SOAG-20 > Project: Overlord > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 1.0 CR1 > Reporter: Gary Brown > Assignee: Gary Brown > > At present, the 'session' property needs to be defined on the first conversation based ESB action within each relevant service descriptor. However the 'session' property is only actually required at runtime in the 'CreateSessionAction' and for the first conversation based ESB action associated with a service descriptor that is the receiver end of a message link (i.e. is receiving a message from an external service). > However from a static validation perspective, the 'session' property is used to obtain information used during validation of the service descriptor, which is why it is currently mandatory within each service descriptor. > It should be possible to work back through the graph to identify the 'session' property, without requiring each conversation based service descriptor to explicitly define this information. If a path back to a service descriptor with the 'session' property cannot be found, then this could be highlighted as a validation error (i.e. orphaned conversation based service descriptor). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] Created: (SOAG-106) Service activity event model

by Gary Brown (JIRA)

Service activity event model ---------------------------- Key: SOAG-106 URL: https://jira.jboss.org/jira/browse/SOAG-106 Project: SOA Governance Issue Type: Task Security Level: Public (Everyone can see) Components: Behavioural Monitoring Affects Versions: 1.0 MR3 Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0 MR3 Definition of event model for reporting service activity from various runtime platforms, and storing the information in a repository. Event model needs to be extensible, although there should be a fixed core of standard events defined. The events could be interaction based, i.e. indicating messages being sent and received, or task based i.e. task started and finished. Data related events could also be stored, when variables are updated. The actual events stored could be dependent upon filters defined in the activity recorders. Question: should the event model be XML based? Or should it support message content being non-xml - i.e. Java objects, or other binary formats? Possible non-XML message contents could be reported in a summarised XML form, to provide enough useful information. The events recorded from a service may be based on local service identity information. This can be used to group events generated by a particular session at a service, but they won't necessarily be business relevant. To be able to correlate service activity, associated with a particular business transaction, across multiple services, it will be necessary to derive business identity that is common across services. However, only some of the reported service activity events may contain the business identity properties - so these should be used to associate the business identity with the local technology specific service/session identity information. -- 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

14 years

1
1
0 / 0

[JBoss JIRA] Created: (SOAG-103) WSDL generation, to accompany generated WS-BPEL

by Gary Brown (JIRA)

WSDL generation, to accompany generated WS-BPEL ----------------------------------------------- Key: SOAG-103 URL: https://jira.jboss.org/jira/browse/SOAG-103 Project: SOA Governance Issue Type: Task Security Level: Public (Everyone can see) Components: WS-CDL Reporter: Gary Brown Assignee: Gary Brown Generate the WSDL associated with a choreography that has been used to generate BPEL process descriptions. Additional BPEL specific aspects (such as partner link types and property alias) could possibly be generated to a separate WSDL file, from the WSDL representing the service interface. -- 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

14 years

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues December 2010