[
https://issues.jboss.org/browse/SOAG-109?page=com.atlassian.jira.plugin.s...
]
Gary Brown closed SOAG-109.
---------------------------
Resolution: Out of Date
Closing as related to old Overlord work which has migrated to other projects. For the
immediate future Overlord and its jira project will be used by some new sub-projects, and
therefore clearing out old issues.
Persistence support for scribble service validator
--------------------------------------------------
Key: SOAG-109
URL:
https://issues.jboss.org/browse/SOAG-109
Project: Overlord
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, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira