[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
[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
[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
[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