1 Reply Latest reply on Oct 29, 2013 4:59 AM by Mauricio Salatino

    JBPM Team's UI Approach - Best Practices

    Tim McClure Apprentice

      I have been evaluating the JBPM technology and I have been impressed with the architecture and design.  I was wondering what the best practices for UI implementation is?  As I understand it GWT is a main component of Errai and UberFire but projects such as DashBuilder appear to be a more traditional JSP/Scriplet approach (possibly because it creates dynamic reports)?  Just looking for some insight in applying GWT for our own application's front end,



        • 1. Re: JBPM Team's UI Approach - Best Practices
          Mauricio Salatino Master

          Hi Tim,

          Both the jBPM Console NG and the Drools WB projects are entirely based on Uberfire (Errai + GWT) so you can look at both to find out best practices about how to implement or extend the functionality provided in KIE - Workbench. Take a look at the jbpm console ng repository: https://github.com/droolsjbpm/jbpm-console-ng/

          You will see there that we have different components inside a single project, and each of those components can be integrated into different distributions. The jBPM Console NG Showcase is just one distribution of all the components that are inside that repo plus some extra components that are required.

          Notice that each component (project inside the repository) has three sub projects called: -api, -backend and -client. I strongly recommend you to follow that approach

          If you are going to create new components. The Dashboard, Form Modeller and Process designer are embedded components that at some point we hope to get migrated to the same technology stack as the rest of the infrastructure.

          I suggest you to read this article if you are interested in how all the pieces fit together and keep on eye on the blogs because I will be posting an example about how to create new screens and components soon.