Camunda Team Blog

The HTML5 parts in camunda BPM

Written by Andreas Drobisch on , under Execution category.
The camunda bpm stacks currently includes three web apps: cycle, cockpit, tasklist. All of them are rewrites from a JSF 2.0 ancestor version and with this post I want to explain the decision to built them on a HTML5 plus REST architecture and not with <insert java web framework here>. Its clear that the web itself is based on the client-server principle. Many Web frameworks like JSF, Vaadin etc. implement it like this: Provide a abstraction layer to define the HTML + JS + CSS Code to generate (Java Code, Facelets etc.) which in the end is your application On request, generate the code sent to the browser, initially create a session model for data binding etc.

A look at the fresh REST API

Written by Thorben Lindhauer on , under Execution category.
camunda BPM comes with a fresh REST API based on JAX-RS. Its goal is to expose the process engine services as broadly as possible. That means we aim to enable you to interact with process engine services via REST with similar expressiveness as in plain Java. With 7.0.0-alpha1, we provide methods such as task querying that already realize our desired degree of detail (similar for process definitions and instances). For future releases, we plan to broaden the scope to reach the afore-mentioned goal.

camunda forks Activiti and launches camunda BPM

Written by Daniel Meyer on , under Execution category.
I am proud to announce that today camunda launches a new open source BPM project: camunda BPM. At this juncture we part ways with the Activiti project which we have contributed to since the first days. Leaving Activiti is a sad but necessary step for us. Starting as a consulting company, we have built a customer base of 250+ in little over 4 years. Last year, we entered the BPM vendor business with the camunda fox BPM platform.