1 2 3 Previous Next 35 Replies Latest reply on Jan 4, 2007 11:32 AM by David Lloyd

    releasing 3.2.Beta1

    Tom Baeyens Master

      test builds seem to work ok.

      developers, is there anything keeping you from releasing the 3.2.Beta1 build ? speak up now or for ever hold your silence.

      Koen, is the version of the gpd in the distro build the right one ? Can you also add the designer release notes from jira to the jpdl/dist/main/resources/runtime/release.notes.html ?

      David, is the web console ready for a release ? After the release i would like to start distributing it to the SE's so that they can start commenting and helping with the layout and navigation. ok ?

      you can try for yourself with the dos test script jpdl/dist/srctest/bin/test.dist.bat. this script does a full clean build, installs the suite and starts the server and the designer.

      linux freaks can read the dos script and translate on the fly to -whatever-shell commands on the fly, right ?

      i'll be back january second. that's when i would like to start the release build. let me know if there is some problem for you with that planning.

        • 1. Re: releasing 3.2.Beta1
          David Lloyd Master

           

          "tom.baeyens@jboss.com" wrote:
          David, is the web console ready for a release ? After the release i would like to start distributing it to the SE's so that they can start commenting and helping with the layout and navigation. ok ?


          I think so, but I've had one comment that some things don't look right in their environment with my latest commits, so I'd just like to verify that first if I could. I've only tested running on Linux with Firefox and (windows) MSIE.

          "tom.baeyens@jboss.com" wrote:
          i'll be back january second. that's when i would like to start the release build. let me know if there is some problem for you with that planning.


          I'm sure everything will be settled by then.


          • 2. Re: releasing 3.2.Beta1
            Koen Aers Master

            I have remarked that there is a problem while using the webapp with a process definition that does not contain a forms.xml file. How are we going to deal with this? Two quick possible solutions:
            - While creating a jbpm project in the designer I always add a forms.xml file. Simple solution that I can do myself, but people who don't need the forms will maybe be upset.
            - Fix the console that it does not throw an error when it does not find the forms.xml file. I have not looked at the console code yet, so I don't see the immediate impact. David what do you think about this?

            Cheers,
            Koen

            • 3. Re: releasing 3.2.Beta1
              Koen Aers Master

              Oh and btw David, the console really looks slick! (though I find the red too red, but that is a personal matter ;-) )

              • 4. Re: releasing 3.2.Beta1
                Ronald van Kuijk Master

                David, regarding the 'doesn't look right' had all to to with the missing/corrupt images. Since I 'fixed' that, it looks the same as with you... The issue of styling remains though...

                • 5. Re: releasing 3.2.Beta1
                  Koen Aers Master

                  We have fixed the FileDefinition class so that it does not throw an error when looking for a file that does not exist. This solved part of the stack trace problem when using the webapp with a processdefinition without a forms.xml file.
                  A related problem remains however. This is when the webapp is used with a processdefinition with tasks for which there is no assiciated taskform. In this case the webapp should not try to render an unexisting form to show the task information.
                  We will nevertheless proceed with the beta1 release.

                  Regards,
                  Koen

                  • 6. Re: releasing 3.2.Beta1
                    David Lloyd Master

                     

                    "koen.aers@jboss.com" wrote:
                    A related problem remains however. This is when the webapp is used with a processdefinition with tasks for which there is no assiciated taskform. In this case the webapp should not try to render an unexisting form to show the task information.


                    Is there a reliable way to tell whether a file exists within a FileDefinition, short of catching the exception?

                    • 7. Re: releasing 3.2.Beta1
                      David Lloyd Master

                       

                      "david.lloyd@jboss.com" wrote:
                      Is there a reliable way to tell whether a file exists within a FileDefinition, short of catching the exception?


                      ...and if not, can we add one? e.g. fileDefinition.containsFile(file) or something like that?

                      • 8. Re: releasing 3.2.Beta1
                        Tom Baeyens Master

                        i have updated the file definition so that a null value is returned if the file doesn't exist.

                        most part of the webapp is updated for this.

                        but the view should be redirected to the process instance view instead of the task instance view in case a process is started without a start task.

                        • 9. Re: releasing 3.2.Beta1
                          David Lloyd Master

                          Ok, no problem, that should be simple to do. Thanks...

                          • 10. Re: releasing 3.2.Beta1
                            Tom Baeyens Master

                            build for 3.2.Beta1 succeeds... but there is still a problem in the web app. when starting a new process instance, it doesn't navigate to the form in case there is one. so the original problem is fixed but it introduced a new problem.

                            david, can you have a look at this asap ? thanks.

                            please, keep me posted when fixing things for an imminent release.

                            • 11. Re: releasing 3.2.Beta1
                              Tom Baeyens Master

                              ah... and david, it would be good if you focus on communication and keep me posted in your morning.

                              then we still have a few extra cycles during our short working time overlap :-)

                              • 12. Re: releasing 3.2.Beta1
                                David Lloyd Master

                                When the process instance starts, it navigates to the task assignment list, if there are tasks... the reason for this (which might be flawed) is that the process may contain, for example, a fork before any tasks, so there could be several tasks initially created. Then you pick the task you are interested in and this brings you to the task instance.

                                • 13. Re: releasing 3.2.Beta1
                                  Tom Baeyens Master

                                  David, please try creating a process in the designer with a wait state and then create a task on the start state. Generate a form with 1 variable for that start task. Deploy and Start It.

                                  Then i was navigated to the process instance view.

                                  Can you see if that is the case for you ?

                                  • 14. Re: releasing 3.2.Beta1
                                    David Lloyd Master

                                    Along the way to verifying this I ran across what looks like a separate bug. I made a process with no tasks in it at all. When you start such a process it should run right through and immediately exit the process. However, what is actually happening is that the TaskMgmtInstance is creating a kind of null task instance that is getting assigned (thus generating an entry in the assignment logs). This task instance has mostly null property values so everything is generating NPEs when trying to view the task.

                                    Shouldn't "taskMgmtInstance.createStartTaskInstance();" return null and not add a task if there is no start task instance? Also, why is this step even necessary? I would think that task instances should be created automatically when a node is entered.

                                    Any clarification is appreciated.

                                    1 2 3 Previous Next