0 Replies Latest reply on Dec 18, 2009 12:15 PM by objectiser

    SAVARA 1.0 Milestone 1 Released

      We are pleased to announce the release of SAVARA 1.0-M1. This is the first milestone release of this new project, and aims to demonstrate how building "testable architectures" can improve the enterprise software development process. A brief outline of "testable architecture" can be found here: http://www.jboss.org/savara

      The release is made up of the following four components.

      1) SAVARA Development Process:

      We have been working to formalise a methodology, based on the principles of "testable architecture", using the Eclipse Process Framework. This can be found at: http://docs.jboss.org/savara/methodology/1.0-M1

      2) SAVARA Eclipse Tools:

      This first version of SAVARA will primarily focus on Eclipse based tooling, with the introduction of web based tooling targeted for the second version. The plugins include the following functionality:

      - Scenario editor (scenarios are used to outline valid conversations between multiple participants)
      - Choreography editor (global model of interactions between participants, encompassing all scenarios)
      - Simulation of Scenarios against Choreography (to validate scenarios are correctly defined in the choreography)
      - Export to BPMN (release includes a working copy of the Eclipse BPMN modeler)
      - Export to HTML (textual description of choreography)
      - Generation of BPEL processes (and WSDL) from Choreography
      - Conformance checking of BPEL processes against Choreography (alpha)
      - Generation of JBossESB Services from Choreography, using "conversation aware" custom ESB actions
      - Conformance checking of JBossWSB Services against Choreography (alpha)

      3) SAVARA Validator:

      The validator is used to monitor message exchanges between services in the JBossESB platform, and validate them against a Choreography description. Currently the monitored interactions, and any inconsistencies that are detected, are temporarily reported via JMS to a Swing based GUI in the Eclipse Tools. In a future milestone, the interaction/error information will be reported via the Service Activity Monitoring (SAM) component of Project Overlord (http://www.jboss.org/overlord) and displayed via a GWT based web console.

      4) SAVARA Runtime:

      This component provides runtime support for the "conversation aware" JBossESB custom actions. These actions serve two functions, firstly they provide execution behaviour for the ESB services in which they are included. However, more importantly, by defining the ESB service using these custom actions, it is possible to statically check the service definition for conformance against a choreography description, and thus ensure that the service will execute as expected.

      The Getting Started Guide, distributed with the Eclipse Tools, is a good place to start. It provides an overview of the tool support available for the different phases of the SAVARA Development Process (or "testable architecture" methodology).

      This is only the first milestone, so there is still alot of work to do, and some of the functionality (i.e. conformance checking) is only at an early stage of development. However hopefully it will provide an introduction into what we would like to achieve over time.

      Feedback would be welcome, whether via the user forum (http://community.jboss.org/en/savara?view=discussions), or by posting feature requests or bugs to our jira (https://jira.jboss.org/jira/browse/SAVARA).