4 Replies Latest reply on Jul 24, 2005 3:37 AM by tom.baeyens

    Evaluating JBpm 3.0

    smaric

      I am evaluating JBpm as a possible candidate for a project that is about to start

      If I look at
      \jbpm-starters-kit-3.0\jbpm\doc\schema\jpdl-3.0.html

      There appears to be no start-state defined

      Then you realise that this is NOT up to date - the schema can be found at
      \jbpm-starters-kit-3.0\jbpm\src\java.jbpm\org\jbpm\jpdl\xml

      If you study the schema you realise that the GPD tool does NOT support a lot of the schema - Super-state, process-state, timer, script ...

      I guess this is NOT too much of a problem as I can hand-craft the process-definition.xml (our Business Analysts won't like this)

      Is there any documentation that tabulates what parts of the schema are supported by the JBpm runtime



      Is the JBpm runtime Monitor going to be able to show the processes diagramatically - ie re-use the GPD to show what state it's in & when/what is completed

      This would also be a useful feature for debugging a process design -
      ie control single step, process breakpoints

      I have used these features in a product - Extricity (don't know if it is still called that) a few years ago














        • 1. Re: Evaluating JBpm 3.0
          kukeltje

          everything you describe besides the singlestep and breakpoints is being worked on. No worries.

          • 2. Re: Evaluating JBpm 3.0
            smaric

            :)
            Good to hear it - BUT what timescales are we looking at
            :)

            • 3. Re: Evaluating JBpm 3.0
              kukeltje

              Depends on how much you contributs ;-)

              Unfortunately, no timescale yet. check the jira for progress on issues and file new ones if you encouter them.

              3.01 will not take to long, 3.1 a little longer.

              Ronald

              • 4. Re: Evaluating JBpm 3.0
                tom.baeyens

                you'll have to redo some part of the learning curve for every workflow/BPM product since none of those tools have common foundations. jBPM is the first tool with solid foundations: "Graph Oriented Programming". So your investment in learning jBPM 3 is very valuable. Cause we will commoditize the BPM software with jBPM, based on a solid model. Good foundations is much more important then features at this point. Adding features goes much faster then changing foundations. In a couple of months we will have a complete features set.

                regards, tom.