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... 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 &... 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 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... New roadmap for review Over the past couple of weeks, a number of new jiras have been created to reflect features that are required over the next year of development. These tasks have been divided into two releases, 1.1.0 and 1.2.0. It is e... Artifact metadata and dependency management Currently artifacts are 'typed' based on information directly added to the artifacts. This is necessary because the different artifact types do not have a common notion of 'behavioural type', and in some cases it may ... Simple CDL Currently Savara is caught between two stages in its evolution - the first being the introduction of the "testable architecture" concept based on the only choreography description language available (i.e. WS-CDL), and... Savara in relation to enterprise architectures Savara aims to deliver the promise of "testable" architectures to solve enterprise problems. However I would like to know from the community out there about how we could extend savara and testable architectures to add... 
Using Drools Guvnor 5.1 as a Service Repository I have spent some time working with the latest version of Drools Guvnor 5.1 to see if it could be used to provide a basic repository for service related artifacts. I have described this on http://community.jboss.org/t... 
SAVARA Roadmap for next year Just before we all go on Christmas holidays, I wanted to get everyone thinking about the SAVARA roadmap for the next year (or even two). We are close to releasing the first milestone for version 1.0, which wil... Docbook support for documentation generation Future documentation generation from within SAVARA is likely to revolve around docbook. Although this can be edited using any XML editor, some initial work has been done within JBossTools to support visualisation of t...
Log in to follow, share, and participate in this community.