5 Replies Latest reply on May 15, 2007 2:45 PM by Maurice Yarrow

    jbpm-jpdl-designer-3.1.0.alpha3 questions

    Maurice Yarrow Newbie

      Hello jBPM community

      The jbpm-jpdl-designer-3.1.0.alpha3 supports a GUI-configurable
      Decision node that works. That's good !

      What I have some questions about are:
      1. When I install the 3.1.0.alpha3 in either jbpm-starters-kit-3.1.4
      or in jbpm-jpdl-suite-3.2.GA, there are no jpg's produced
      by the graph designer, and hence, upon deploying to JBoss,
      there is no diagram monitoring.

      2. What happened to the controller panel for configuring user-input
      parameters in a swimlane task ?


      Maurice Yarrow
      SplashNote Systems
      Santa Clara, California

        • 1. Re: jbpm-jpdl-designer-3.1.0.alpha3 questions
          Koen Aers Master

          Hi Maurice,

          I am not aware of the jpg issue. Are there particular errors showing up in the Eclipse error log?
          Btw, I released alpha4 earlier this week. It has complete jPDL support, including controller support for tasks and form generation. I recommend that you give it it a try.

          Regards,
          Koen

          • 2. Re: jbpm-jpdl-designer-3.1.0.alpha3 questions
            Maurice Yarrow Newbie

            Hello Koen

            Thanks for replying about the jpdl alpha3 issues.

            1. With respect to the presence of the jpeg (for monitoring),
            I have to make sure that the jpeg is being included in the
            deploy (of course) and what I had found is that unless I
            carefully "clean" the eclipse project, there was (only sometimes)
            some issue with this. So this is no longer an issue.

            2. I will take your advice and try the jpdl alpha4. Which brings me
            to the current issue. I am running jpdl alpha3 in the
            jbpm-starters-kit-3.1.4 because I could not get the following
            signalling servlet to work with the jbpm-jpdl-suite-3.2.GA release.

            I am including the relevant code below. I looked at the 3.2.GA
            jbpm runtime lib javadocs and see nothing particularly obvious
            that would indicate that the code (which works fine in 3.1.4) is no
            longer compliant with 3.2.GA.

             JbpmConfiguration jbpmConfiguration = JbpmConfiguration.getInstance();
             JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext();
             ProcessInstance processInstance = null;
             try {
             processInstance = jbpmContext.loadProcessInstance(processInstanceId);
             etc., etc., ...
            


            With the 3.2.GA runtime, there are a series of either classes or
            ...hbm.xml files that are not found. This problem does not exist
            when using the 3.1.4 runtime.

            Question: is there a new model for getting the ProcessInstance ?


            Maurice Yarrow
            SplashNote Systems
            Santa Clara, California



            • 3. Re: jbpm-jpdl-designer-3.1.0.alpha3 questions
              Koen Aers Master

              Hi Maurice,

              This is a configuration issue. Try to change the configuration files in the project created with the GPD by replacing them with the ones coming with the jBPM distribution.
              Let me know if this helps. Better yet, create a JIRA issue so that I remember to change this and include it in one of the upcoming beta's.

              Regards,
              Koen

              • 4. Re: jbpm-jpdl-designer-3.1.0.alpha3 questions
                Maurice Yarrow Newbie

                Hello Keon

                So I followed your suggestion, and am using
                the jpdl-3.1.0.alpha4. I am using this with
                the 3.1.4 runtime but everything seems to be
                working.

                I have an actionHandler question, for which I have
                not found a documentation answer:

                Question: In the actionHanderl Properties
                dialog, is there a Config Type Field setter
                dialog for setting "Fields" (which then are
                represented in the processdefinition.xml with
                something like the following:

                <action class="org.test.MyAction">
                 <city>Atlanta</city>
                 <rounds>5</rounds>
                </action>
                

                Note: this is from jBPM Userguide 16.2.3.1
                config-type field)

                When I set an actionHandler Config Type to
                "Field", I do not subsequently see a mechanism
                for entering field names and values in the
                action Properties dialog. Is this correct or am
                I missing something that allows me to set
                the field-name / value pairs for an actionHandler?

                I might rephrase my question to the following:
                When a user is designing a workflow, how can
                this user set actionHandler config-type Field
                values (other than having to write XML into
                the processdefinition.xml source) ?

                Maurice Yarrow
                SplashNote Systems
                Santa Clara, California


                • 5. Re: jbpm-jpdl-designer-3.1.0.alpha3 questions
                  Maurice Yarrow Newbie

                  Hello Koen and jBPM community

                  OK, so I answered my own question about
                  the delegation actionHandler Config-type Field
                  and getting it to prompt for field values in the
                  designer action properties dialog. The solution
                  was (after adding an appropriate instance variable
                  into the particular actionHandler in question) to
                  go into the Properties dialog for the action and
                  to place the cursor after the name of the
                  actionHandler class and to press "enter" on the
                  keyboard. This then (evidently) causes the
                  designer to re-evaluate the actionHandler class
                  for any code changes and then it recognizes the
                  presence of a new instance variable.

                  Maurice Yarrow
                  SplashNote Systems
                  Santa Clara, California