July 2009 - overlord-issues - Jboss List Archives

[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

1
2
0 / 0

[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

1
1
0 / 0

[JBoss JIRA] Created: (SOAG-113) Report service validator events to SAM instead of JMS

by Gary Brown (JIRA)

Report service validator events to SAM instead of JMS ----------------------------------------------------- Key: SOAG-113 URL: https://jira.jboss.org/jira/browse/SOAG-113 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 Report Service Validator activity and errors direct to SAM, using the SAM API and the new service instance based event model (SOAG-111). -- 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-96) Stateless jboss-esb.xml generated incorrectly for Broker example, when perform set to async

by Gary Brown (JIRA)

Stateless jboss-esb.xml generated incorrectly for Broker example, when perform set to async ------------------------------------------------------------------------------------------- Key: SOAG-96 URL: https://jira.jboss.org/jira/browse/SOAG-96 Project: SOA Governance Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 1.0 MR1 Reporter: Gary Brown Assignee: Gary Brown The ESBBroker example, Broker role - when generated as a stateless ESB service, the jboss-esb.xml is not as expected when the perform inside the while loop is async. The expected behaviour is correctly generated when the perform is synchronous. Need to investigate why this is inverted, and what the correct behaviour should be in both cases. -- 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
3
0 / 0

[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

1
1
0 / 0

[JBoss JIRA] Created: (SOAG-78) Rebuild conversation aware sample jboss-esb.xml configurations to be based on generated version

by Gary Brown (JIRA)

Rebuild conversation aware sample jboss-esb.xml configurations to be based on generated version ----------------------------------------------------------------------------------------------- Key: SOAG-78 URL: https://jira.jboss.org/jira/browse/SOAG-78 Project: SOA Governance Issue Type: Task Security Level: Public (Everyone can see) Components: WS-CDL Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0 MR2 Samples for conversation aware actions should be based on generated version, to make it easier for end-user to generate a new skeleton of the behaviour from the choreography, and compare it against the fully implemented version. -- 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

[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

1
1
0 / 0

[JBoss JIRA] Created: (SOAG-72) Business pojo class can't be hot-deploy

by Jeff Yu (JIRA)

Business pojo class can't be hot-deploy ---------------------------------------- Key: SOAG-72 URL: https://jira.jboss.org/jira/browse/SOAG-72 Project: SOA Governance Issue Type: Bug Security Level: Public (Everyone can see) Components: Conversation Runtime Affects Versions: 1.0 MR1 Reporter: Jeff Yu Assignee: Jeff Yu The steps to reproduce: 1. Deploy the overlord cdl to JBoss ESB. 2. Run the purchasing example. 3. Open the common/creditAgency/src/com/acme/services/creditAgency/CreditAgencyPurchase.java Make the isCreditValid() method return false; 4. Redeploy the creditAgency esb artifact. 5. The update won't take effect by using hot deploy. -- 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

15 years, 4 months

1
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues July 2009