4 Replies Latest reply on Aug 29, 2014 5:15 PM by Kris Verlaenen

    JBPM Development Process

    Stephen Munro Newbie

      Hello,

       

      I have a small question regarding how one goes about developing a JBPM solution.  So far, I have created my own repository/project and created a diagram with a collection of tasks. I also understand GIT and Maven are used internally by the tool for project structure and version control. My question is how should I work with Java code. Ideally, I'd like to export the workflow from KIE and import into Eclipse (or any ide for that matter) and complete the Java code (service implementation) using the tools provided by the IDE. If what I understand is correct, the Java code is supposed to be done on the KIE-WB tool. This means I lose the power of the features an IDE gives me such as debugging. With KIE the best I can do is put System.out.println statements in and simulate the process to catch errors, which would be chaotic for a large workflow.

       

      I am very new to JBPM and my understanding of the above may be flawed. I'm assuming there are recommended approaches for dealing with them, if anyone could point me in the right direction, that would be awesome.

       

      Warm regards,

       

      Stephen Munro

        • 1. Re: JBPM Development Process
          Stephen Munro Newbie

          My web searching skills could do with some refining...I found this article, which seems to point people in the correct direction: how to deploy processes in jBPM 6? | Planet JBoss Developer

           

          I've yet to work my way through it, but it answers a lot of questions.

          • 2. Re: JBPM Development Process
            Kris Verlaenen Master

            It is recommended to separate Java code that is not immediately part of the processes etc. (like service implementations etc.) in a separate project so you can build and deploy using your normal development cycle.  This jar can then be added to your server or as a dependency to specific projects (after uploading the war to the workbench through the UI).  This allows this kind of Java integration code to live independently and be managed using your normal development tools and cycle.

             

            Alternatively, you could also still keep this Java code as part of your project on the workbench, yet use the git integration between your IDE and the workbench to do the changes related to these Java classes.  We wouldn't expect you to edit this files on the workbench, but your developers could push them into the project using the git integration.

            • 3. Re: JBPM Development Process
              Stephen Munro Newbie

              Thanks Kris, what you have described. I haven't tried using a distinct JAR.  My initial impression was that anything relating to the process such as script tasks, service tasks etc, should be grouped into one deployment.  Unfortunately, the latest book on JBPM doesn't have much to say on ServiceTasks, so I'll need to dig out some non JBPM 5 git hub examples, which seem to be in short supply . Again that could be due to my poor web search skills.

               

              Regarding the IDE > Maven integration. I am having a problem with making a project appear on the workspace. So, if I create a repository called 'org.dev.smunro' and I created a JBPM maven project in Eclipse and attempt to publish through SSH, I can't a new project appear for the repository. I can see the project was committed into the internal git, but I was expecting the workbench to generate a project. Is this the case? If so, can you point me at a guide to achieve this? Even a JBPM 6 maven project with the required details I can attempt to upload and use for reference?

               

              Warm Regards,

              Stephen Munro