Execution Server Remote API Page - mrietveld/jbpm GitHub Wiki

Home1-Pager: Execution Server (Unification) Remote API
2015-04-08

Overview

The overall goal here is to create two execution servers (1 for drools, 1 for jBPM) that build on the work that Edson did when creating the kie-server modules in 6.2.

My task here is to design, unifiy, implement and provide the tests for the Remote API used by both execution servers.

Goals

A basic remote API (REST, JMS and WS/SOAP) that allows all users to do basic operations with the execution servers.

Ideally, as much code as possible for the remote API infrastructure will be shared between the 2 servers for readability and maintability.

Primary 6.3.x goals

  • Drools REST API
    • rules?
  • jBPM REST API
    • processes
    • tasks
    • history
    • deployments?
  • JMS MDB's
    • Drools
    • jBPM
  • Documentation

Nice-to-have

  • jBPM REST API
    • query
    • client
  • Web services
    • processes
    • tasks
    • history
    • deployments
    • query
    • client
  • JMS
    • client

Current Status

2015-04-08: initial work done, no full design yet

Work Plan

Work my but off and get it done by June 1rst, 2015

Deadlines

At least a minimal remote API for the exec server must be done by June 1rst!

Task Breakdown

  • REST Design
  • REST implementation and tests
    • simultaneous documentation
  • JMS Design
  • Unification code at appropriate points

Later:

  • Webservice design
  • Webservice implementation and tests
    • simultaneous documentation

Coordination with other teams

  • QA
    • share documentation of features
    • show tests
  • Documentation
  • Product
    • inform about new modules
⚠️ **GitHub.com Fallback** ⚠️