4 Replies Latest reply on Apr 24, 2009 10:06 AM by koen.aers

    Bugs in GPD jBPM 3.2.6.SP1

    salaboy21

      I'm trying to teach about jBPM, that is very user friendly and very easy to use, and I was disappointed when I found two bugs, that confuse and scared new users.

      The first one the missing activation.jar with the fix proposed in this forum:
      http://www.jboss.org/index.html?module=bb&op=viewtopic&t=153600
      where the solution points to a fix proposed to version 3.3.0. So, my user will say.. we found bugs and we are not using the last version of the framework.. very bad..

      The second bug that I found, when you fix the activation.jar problem and create a new project with the sample process.. the sample process is never created.. so my users said.. wtf!! I put to create a sample process but i got nothing.. and all of them freaks out..

      So, please.. in order to get user and not loose the new ones that try to begin with the framework, fix this issues for this version of GPD.
      Thanks, your feedback will be appretiated.

        • 1. Re: Bugs in GPD jBPM 3.2.6.SP1
          kukeltje

          Mauricio,

          please file Jira issues for this if they are not already there (vote for them in that case). That helps more then just posting here.

          • 2. Re: Bugs in GPD jBPM 3.2.6.SP1
            salaboy21

            I will do that.. but I was waiting some feedback.. to know that are not only my problems.

            • 3. Re: Bugs in GPD jBPM 3.2.6.SP1

              The issue is discussed in this closed jira issue:

              https://jira.jboss.org/jira/browse/JBPM-1420

              It seems that the participants thought that everything would be OK while it is not (at least not in 3.2.6.SP1).

              Volker

              • 4. Re: Bugs in GPD jBPM 3.2.6.SP1
                koen.aers

                This is actually not really a GPD issue but an issue with the runtime. The runtime publishes information (contained in the version.info.xml file and some other locations) on which the GPD relies to create the project and the sample files.
                The problem is that this file was moved and that the info was not kept up to date by Thomas at the moment when he restructured the project and it's build.
                So far the explanation. As for the solution, I can build one hundred new GPD releases but as long as these are going to be used with the flawed runtime release the problem is goint to persist. So either the runtime needs to be patched per the described procedure or the GPD has to be used with a runtime release that publishes the correct information. If you guys know of any runtime that produces the flaw please report it in JIRA with the correct versioning information.

                Regards,
                Koen