[JBoss JIRA] Created: (SOAG-64) Deletion of grouping constructs
by Gary Brown (JIRA)
Deletion of grouping constructs
-------------------------------
Key: SOAG-64
URL: https://jira.jboss.org/jira/browse/SOAG-64
Project: SOA Governance
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Tooling
Affects Versions: 1.0 CR1
Reporter: Gary Brown
Assignee: Gary Brown
Currently, deletion of actions from the jboss-esb.xml file only occurs for simple activities (e.g. sends/receives and perform).
The problem with deleting grouping constructs is that, not only has the main construct got to be deleted, but the ESB service descriptors related to each path needs to be removed, potentially with further linked service descriptors.
In some cases, it will also be necessary to identify the 'join' service descriptor, and insert a ScheduleStateAction to transition to this service descriptor. Where the join service descriptor not explicitly defined in the grouping construct, it may possibly be inferred based on the following following action in the description - if one has been defined. Otherwise it may have to be inferred by examining each path, to determine where they converge.
--
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
[JBoss JIRA] Created: (SOAG-107) JBossESB service activity adapter
by Gary Brown (JIRA)
JBossESB service activity adapter
---------------------------------
Key: SOAG-107
URL: https://jira.jboss.org/jira/browse/SOAG-107
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
JBossESB 4.x service activity adapter for intercepting appropriate events and reporting them using the service activity event model.
Adapter should provide a filter mechanism that can be based on:
1) the message type - so only report certain event types
2) event type - only report certain event types
3) message content filter - to extract relevant information from the message content instead of sending the complete message, in situations where the data is too large
--
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
[JBoss JIRA] Created: (SOAG-111) Base event model for reporting Service related activity information
by Gary Brown (JIRA)
Base event model for reporting Service related activity information
-------------------------------------------------------------------
Key: SOAG-111
URL: https://jira.jboss.org/jira/browse/SOAG-111
Project: SOA Governance
Issue Type: Task
Security Level: Public (Everyone can see)
Components: SAM
Affects Versions: 1.0 MR3
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0 MR3
Define event model for carrying process/service instance - initially targeted towards process governance service validators.
Investigate use of BPAF, as base process/service event model, although concept of identity (derived from business tokens, as in WS-CDL and BPEL) needs to be accommodated, as well as a instance identifier (which is server implementation specific). This is necessary to be able to correlate service instance information, across multiple co-operating services, to a business transaction instance.
--
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
[JBoss JIRA] Created: (SOAG-108) Migrate pi4soa based Service Validator to Scribble monitor
by Gary Brown (JIRA)
Migrate pi4soa based Service Validator to Scribble monitor
----------------------------------------------------------
Key: SOAG-108
URL: https://jira.jboss.org/jira/browse/SOAG-108
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
Currently the use of the pi4soa monitor within the service validator means that only a WS-CDL (i.e. CDM) description can be used to monitor the behaviour of a service against a choreography.
A scribble based monitor would be able to perform runtime service validation from a range of source representations.
As part of doing this work, the service validation architecture should also be changed to feed off the service activity event model, instead of being co-located with the service.
--
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