Project Plan For soa.stardust, version Kepler
- business processes functinality in Eclipse or alternatively in a browser-based environment,
- integration functionality for applications, services and UI components,
- runtime exection of processes
- browser-based access to BPM functionality via portal applications
This project plan lays out features and schedule for the Kepler release of project Stardust.
Stardust Kepler will deliver the following main components:
- Modeling plugins to create and debug workflow models from within eclipse.
- Stardust process engine to execute BPM applications on various java-based runtime environments.
- Stardust web portals for browser-based execution and monitoring of business processes and associated applications.
- Browser-based modeler for creating and deploying workflow models directly in browser environments.
- Reporting component (BIRT based) for runtime monitoring and reporting of BPM applications.
- Integrated rapid application environment (RAD) for deploying and executing BPM applications in an embedded Tomcat server within the eclipse modeling environment.
- Possibility to consume the Stardust runtime as a Maven dependency in build files of consuming projects and to automatically configure runtime deployments by consuming Maven archetypes.
First integration build
Juno support established. Main platform issues known to date addressed for Kepler.
Supported Eclipse Platform
Goal is that the Stardust Kepler Release will be compatible with eclipse platform versions Kepler (4.3) as well as Juno (4.2).
Runtime Platform Upgrades
- MS SQL Server 2012
- JBoss Application Server 7.1
- Tomcat 7
Enhanced Maven Support
- The Stardust build files will be refactored to fully rely on Maven mechanisms and eliminate other build technologies wherever possible.
- Consumption of the Stardust engine with its transient dependencies via Maven will be further simplified for consuming projects.
- Maven archetypes will be provided that allow for automated assembly of Stardust server deployments.