Skip to main content
Jump to: navigation, search



VIATRA CEP Roadmap for Q4 2014 and Q1 2015

Last revised October 23, 2014

Please send comments about this draft plan to the developer mailing list.

For the currently active bugs, see the related page in the Bugzilla.

First release

There is no scheduled date for the first official release of the restarted VIATRA project, but it is expected to go in Q2/Q3 of 2015. In the context of the CEP extension, we follow the checkpoints below.

Checkpoint 1: DSL stabilization

  • Fixes, but no enhancements for the DSL
    • Typical issues: inconsistent code generation from patterns, shortcomings of the IDE while designing patterns, IncQuery integration
  • Targeted date: 2014/Q4 -- December 18
  • Changes
    • Support for nested complex event expressions (29/11/2014)
    • Upgrade to Xtext 2.7 (29/11/2014)
    • fixed [441088] (1/12/2014)

Checkpoint 2: Supporting services

  • Generated factories, interfaces should be revised in order to enable more efficient and component-oriented reuse of the event model
    • Typical issues: too much coding required for putting the engine to work (common use-cases should be considered), GUI support (e.g. wizards) are not working with E4.4, project builder, automatic dependency management, unit and integration test packages
  • Targeted date: 2015/Q1 -- January 31
  • Changes
    • Wiki pages (previously planned for Checkpoint #4 at the end of Q1/2015) (11/01/2015)
    • Revised and helper class (14/01/2015)
    • Fixed (15/01/2015)
    • Support for quasi-point model event semantics (syntax, generator) (18/01/2015)
      • Related change in the syntax: the "iqChangeType" attribute in ComplexEventPatterns became optional. If not specified, point semantics are assumed.
    • GUI face lift (18/01/2015)
    • Change in the syntax: "uses" became "import" (18/01/2015)
    • Change in the syntax: "IQPatternEvent" became "QueryResultChangeEvent", see 457795
      • Also changed the model structure: the concept of "PackagedModel" is now removed from the hierarchy and model elements are placed directly under the EventModel root. Related changes: formatter, syntax highlight, outline providers, etc.
    • Introduced the AtLeastOnce operator ({+}) and made the UNTIL operator obsolete. It will be used to depict temporal relations, e.g. between events triggered upon found and lost pattern matches. (24/01/2015)
    • Prepared the project for a new project builder. Will be implemented in the next milestone.
    • Added DSL tests plugin.

Checkpoint 3: Tool stabilization

  • Targeted date: 2015/Q1 -- February 28
  • Changes

Checkpoint 4: M2

Checkpoint 5: M3

Back to the top