Activity information for conversations The activity information that needs to be captured for the conversation based actvity events needs to be indexed on two concepts: (a) business context This is termed 'business' context at the moment du... 
Savara Web App Style Hi Just wanted to start a discussion on the Savara Web App - not necessarily focusing on functionality at the moment, but more on style. As developers we are used to an IDE (integrated development envi... Hudson jobs for git repos Now that the core bundles are separated into a separate git repository, I have also setup a separate hudson job to build these bundles. The idea being that hudson jobs will also be setup for the savara-integra... Savara 2 code moving to github In common with a number of jboss.org hosted projects, we have decided to move development from svn to git hosted at github. The repository will be hosted at https://github.com/organizations/savara. In ... Milestones for Savara 2 As mentioned in other posts, the main goals moving from Savara 1 to 2 are: 1) Change from being Eclipse centric to be Web based with Eclipse tooling support where appropriate 2) Integrate with a SOA Re... Activity monitoring and process mining Have just created a feature request for Savara2 related to this: https://issues.jboss.org/browse/SAVARA-164 Currently Savara does not persist any activity information. The service validators simply publish 'se... Design Note: Activity Monitoring/Management in SAVARA This design note will capture design information concerning the activity monitoring and management within Savara. Note: the scope of this work is not intended to provide a full scale Service or Business Activi... datasource and properties file for RDBMS session store Hi Gary, In the process of implementing the RDBMSSessionStore class, I still need following two files: 1. data source configuration file, things like jdbc url, username & password etc. 2. properti... 
Review of RDBMS session store Hi Jeff Great work - and very quick Only a few comments: 1) DummySession could probably be moved to the src/test/java? 2) Transaction Manager - although providing an option to pass one... Questions on the SessionStore API Hi, I was working on implementing the RDBMSSessionStore class, and then got following observations on the SessionStore API. 1. For the create method in the API, we currently have as following: &#... Savara SOA Repository Requirements This document outlines the SAVARA requirements for a SOArepository. Artifact management: Upload individual and groups of artifacts Find artifacts based on artifact type and possibly artifact type spe... 
Savara SOA Repository Requirements This document outlines the SAVARA requirements for a SOArepository. Artifact management: Upload individual and groups of artifacts Find artifacts based on artifact &... Savara 2: Scenarios In Savara 1, we use the pi4soa scenarios that are WS-CDL specific and require a direct reference to the CDM choreography file with which they are associated, to enable them to be simulated against that choreography. &... Savara 2 : How to manage dependencies for validation In a previous thread (http://community.jboss.org/thread/153044?tstart=0) I introduced the idea of a project descriptor (called TIA in the thread), that has been partially implemented in Savara 1.1. The role of... Savara usability improvements I would like to discuss a range of usability improvements. I think the current developer/architect focused tooling could be improved to make it easier to use and less error prone. I also would like to extend the gener... 
Savara 2: Architect roles Currently there are six roles defined in the Architect category of the SAVARA SOA Development methodology. As mentioned in the other related thread, it is possible for a user to perform one or more roles, so this does... Savara 2: Analyst roles In the SOA Development methodology, it defines three analyst roles: Business Analyst "This role has an extensive knowledge of the business domain as well as a technical background that includes business ... Looking forward to Savara 2 Savara 1 is essentially a small set of Eclipse based tools looking to provide some support for the Testable Architecture methodology. It is a bit more than that, as it also includes runtime validation of Web Services/... Plan for making plugins available within JBossTools Currently the bulk of the plugins used by Savara live outside of JBoss Tools. The only plugins that live within JBoss Tools are the pi4soa Choreography Description editor tools. This will remain the situation for Sava... TIA Project Descriptor This thread follows on from the 'Artifact metadata and dependency management' thread - which was more about how to represent dependencies between resources in different repositories. This thread will focus mor...
Log in to follow, share, and participate in this community.