December 2009 - overlord-issues - Jboss List Archives

[JBoss JIRA] Created: (SOAG-115) create a overlord maven2 repo that contains unmavenized jars, like jbossesb rosetta.

by Jeff Yu (JIRA)

create a overlord maven2 repo that contains unmavenized jars, like jbossesb rosetta. ------------------------------------------------------------------------------------ Key: SOAG-115 URL: https://jira.jboss.org/jira/browse/SOAG-115 Project: SOA Governance Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 1.0 MR2 Reporter: Jeff Yu Assignee: Jeff Yu Fix For: 1.0 MR3 Learned this both from jBPM and Riftsaw, they have their own little maven2 repo to contain those unmavenized jars, so that users don't need to install these jars locally. -- 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
5
0 / 0

[JBoss JIRA] Created: (SOAG-110) Remove the conversational esb actions. (stateful one)

by Jeff Yu (JIRA)

Remove the conversational esb actions. (stateful one) ----------------------------------------------------- Key: SOAG-110 URL: https://jira.jboss.org/jira/browse/SOAG-110 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Conversation Runtime Affects Versions: 1.0 MR2 Reporter: Jeff Yu Assignee: Jeff Yu Fix For: 1.0 MR3 Will remove the conversational esb actions, as we found it is complex to use, compare to the stateless approach that we've introduced in the M2 release. tasks are: 1. Remove those actions and samples. 2. Update the package name of stateless actions. 3. Restructure the samples. -- 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
3
0 / 0

[JBoss JIRA] Created: (SOAG-114) rename the package name "org.jboss.overlord.cdl" package.

by Jeff Yu (JIRA)

rename the package name "org.jboss.overlord.cdl" package. --------------------------------------------------------- Key: SOAG-114 URL: https://jira.jboss.org/jira/browse/SOAG-114 Project: SOA Governance Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 1.0 MR2 Reporter: Jeff Yu Assignee: Jeff Yu Fix For: 1.0 MR3 update it into org.jboss.savara, as we combined the cdl sub-project and savara. -- 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-112) Service Activity Console

by Gary Brown (JIRA)

Service Activity Console ------------------------ Key: SOAG-112 URL: https://jira.jboss.org/jira/browse/SOAG-112 Project: SOA Governance Issue Type: Task Security Level: Public (Everyone can see) Components: SAM Affects Versions: 1.0 MR3 Reporter: Gary Brown Assignee: Heiko Braun Fix For: 1.0 MR3 Service activity visualisation, initially aimed at presenting information generated by the Overlord Process Governance Service Validators. Three main views are required: 1) Service instance summary This should be a tabular view of the service instances, defining high level information such as the service instance id, name, status. It would be good if the rows could be colour coded to reflect the highest error state - e.g. warning = yellow, error = red. Normal could just be grey/black, rather than green. 2) Service instance details When a service instance is selected from the summary view, the Service Instance Details view should show a list of the events that are associated with the service instance. The details for the rows will include timestamp, event summary, event status. 3) Service activity event details When a service instance event is selected, enable the event payload to be presented - initially just as XML, although eventually this could be transformed into a suitable presentation representation (if a definition is available). A fourth view may also be required to just show error messages, although this could be combined with (1). View (1) should also provide a filtering mechanism, which eventually should enable filtering based on business attributes. But for the initial release, it should be possible to filter based on time range. The event stream will be based on an event model defined in issue https://jira.jboss.org/jira/browse/SOAG-111 For this initial version, the console will only operate on current events - there won't be any persistence support, or querying of historic events. -- 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-50) Fix EP samples on Drools Fusion impl

by Heiko Braun (JIRA)

Fix EP samples on Drools Fusion impl ------------------------------------ Key: SOAG-50 URL: https://jira.jboss.org/jira/browse/SOAG-50 Project: SOA Governance Issue Type: Task Security Level: Public (Everyone can see) Components: SAM Reporter: Heiko Braun Assignee: Heiko Braun <excludes> <exclude>org/jboss/test/sam/samples/pattern/PatternTestCase.java</exclude> <exclude>org/jboss/test/sam/samples/aggregation/FilteringTestCase.java</exclude> <exclude>org/jboss/test/sam/samples/falloff/FalloffTestCase.java</exclude> <exclude>org/jboss/test/sam/samples/aggregation/AggregationTestCase.java</exclude> </excludes> -- 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
1
0 / 0

[JBoss JIRA] Created: (SOAG-79) Support jBPM

by Mark Little (JIRA)

Support jBPM ------------ Key: SOAG-79 URL: https://jira.jboss.org/jira/browse/SOAG-79 Project: SOA Governance Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment, WS-CDL Affects Versions: 1.0 MR1 Reporter: Mark Little Assignee: Mark Little -- 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-109) Persistence support for scribble service validator

by Gary Brown (JIRA)

Persistence support for scribble service validator -------------------------------------------------- Key: SOAG-109 URL: https://jira.jboss.org/jira/browse/SOAG-109 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 The behavioural sessions, constructed within the scribble monitor when processing service activity information, can optionally be stored in a database. This means that as each relevant service activity event is received, the current behavioural session will be retrieved from the database, and used to evaluate the next service activity message. The other approach would be to evaluate the complete history of events, for a particular service session, when the next service activity event for that session occurs. This approach means that intermediate session information does not need to be stored, and it could also mean that the session could be evaluated against services as the description is updated (although this may depend on what type of versioning is used - i.e. it may actually need to use the old version of the process description). -- 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
3
0 / 0

[JBoss JIRA] Created: (SOAG-77) Trailblazer example documentation improvments

by Jeff Yu (JIRA)

Trailblazer example documentation improvments --------------------------------------------- Key: SOAG-77 URL: https://jira.jboss.org/jira/browse/SOAG-77 Project: SOA Governance Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 1.0 MR1 Reporter: Jeff Yu Assignee: Mark Little Fix For: 1.0 MR2 Thanks Jeff Delong for following suggestions and feedback. ------------------------ A few suggestions on how to improve the documentation: 1) Have the readme refer to the docs/samplesguide/SamplesGuide. While much of the information is redundant, the SamplesGuides has the information on the ChoreographyMonitor and the error-client. 2) In the SamplesGuide.pdf, the code snippet from LoanBroker.java is unreadable. 3) Under 10 2 It says to run the commands from step 6 on. Is that really necessary? 4) Add more information on the role of the LoanBroker.java class, and how it's choice of if (score >= 4) { //step 3a - send to Bank - async System.out.println("sending to first Bank..."); sendToBank(bank1Invoker, customer, "b1"); Implements the Choreography conditional expression: cdl:getVariable('creditCheckResult','','//@score') >= 4 5) It would be nice to have an architectural discussion here about how this choreography is being monitored. (perhaps this is described in another document I have yet to read). -------------------- -- 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
4
0 / 0

[JBoss JIRA] Created: (SOAG-68) Async Perform

by Gary Brown (JIRA)

Async Perform ------------- Key: SOAG-68 URL: https://jira.jboss.org/jira/browse/SOAG-68 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Jeff Yu Currently the Brokerage example iterates through a list of suppliers to find the best quote, before proceeding to perform a credit check and complete the transaction. However the list of suppliers is processed using a loop containing a synchronous perform, so each supplier is dealt with in turn. The next step is to cater for an asynchronous perform, where the suppliers can be dealt with concurrently (i.e. so multiple sub-sessions active at the same time). This would require the 'WhenAction' to block, awaiting all of the sub-sessions to complete, before making its decision regarding the best quote. -- 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
3
0 / 0

[JBoss JIRA] Created: (SOAG-105) Service activity repository

by Gary Brown (JIRA)

Service activity repository --------------------------- Key: SOAG-105 URL: https://jira.jboss.org/jira/browse/SOAG-105 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 Persistence storage for service activity information. Information will be received from a variety of event sources reporting service activity information - which will then be persisted in the database. Information enrichment needs to be supported. This can be in the form of extracting conversation identity information, or other custom properties, which can then be used to query the service activity information. NOTE: Although the storage of service activity information could be used to trigger a variety of activities, including deriving the properties described above, as well as performing higher level validation, the behavioural validation is dependent upon the conversation identity fields - and therefore it may be better to derive this base information when recording the service activity information. But other information and validation tasks can be triggered based on the storage of the service information - possibly using DNA at some point (i.e. the sequencing mechanism). -- 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
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues December 2009