8 Replies Latest reply on Mar 16, 2007 11:53 AM by Ronald van Kuijk

    jBPM jPDL GPD 3.1.0 alpha3 released

    Koen Aers Master

      Hi all,

      Yesterday, I released the jBPM jPDL GPD release 3.1.0 alpha3. The most relevant updates are decision node configuration and support for configuration of all action elements.

      You can download and try out the new release from our sourcefource download pages: http://sourceforge.net/project/showfiles.php?group_id=70542&package_id=116692&release_id=489757.

      Don't hesitate to report bugs and problems in JIRA: http://jira.jboss.com/jira/browse/GPD.

      Cheers,
      Koen

        • 1. Re: jBPM jPDL GPD 3.1.0 alpha3 released
          Bernd Ruecker Master

          Hi Koen!

          Nice thing, the new GPD :-) Thanks a lot for introducing support for super states, thats really, really cool!

          I have some very basic problems with the plugin, but I have not found any JIRA issues for that. because I am always a little bot confused which comes from Eclipse or plugins, i will first list them here, but if you want to, I can make JIRA issues of course.

          Here we go:

          - if i add transitions in the XML, they are not visible in the graphical designer

          - If I use super states, some transitions are potining in the totally wrong direction, at least afte rclosing and opening the diagram, you can see a example here http://www.camunda.com/downloads/gpd_screenshot.png

          - If I delete a node in the XML, it is still visible in the diagram. If I want to delete it there, nothign happens. After closing and reopening the diagram, the state is gone.


          I think, not big issues, but these limitate the use of the designer a lot....

          But good work with the new designer :-)
          Thanks and regards
          Bernd

          • 2. Re: jBPM jPDL GPD 3.1.0 alpha3 released
            Bernd Ruecker Master

            I played around with the tool a little bit more and I am not really shure what happens.

            I think the main problem is, that in the source added transitions are not shown in the diagram. After then adding them there I had some confusing with Transitions (some duplicates, some invalid, ...).

            So I removed all transitions from the source xml, reopened the diagram and draw everything by hand. after that, the diagrams looks like it should.

            If you can fix the problem, that added transitions in the source are shown in the diagram, maybe the biggest problems are gone then...

            • 3. Re: jBPM jPDL GPD 3.1.0 alpha3 released
              Koen Aers Master

              Hi Bernd,

              Thanks for the feedback. The XML synchronization with the graphical view is not working fully yet. That will be acted upon the coming weeks. It should be ready for the beta releases.

              Cheers,
              Koen

              • 4. Re: jBPM jPDL GPD 3.1.0 alpha3 released
                Bernd Ruecker Master

                Allright.

                I had some new strange errors now, while deleting a transition Eclipse crashed and if I now try to open the process diagramm, i get a Exception:

                !ENTRY org.jbpm.gd.jpdl.ui 4 0 2007-03-01 14:28:58.921
                !MESSAGE Could not create graphical viewer
                !STACK 1
                org.eclipse.ui.PartInitException: Error reading contents of file : gpd.xml.
                 at org.jbpm.gd.jpdl.ui.editor.JpdlContentProvider.addGraphicalInfo(Unknown Source)
                 at org.jbpm.gd.jpdl.ui.editor.JpdlGraphicalEditorPage.initInput(Unknown Source)
                 at org.jbpm.gd.jpdl.ui.editor.JpdlGraphicalEditorPage.init(Unknown Source)
                 at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:179)
                 at org.jbpm.gd.jpdl.ui.editor.JpdlEditor.addGraphPage(Unknown Source)
                 at org.jbpm.gd.jpdl.ui.editor.JpdlEditor.createPages(Unknown Source)
                 at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:276)
                 at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:596)
                 at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
                 at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
                 at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:214)
                 at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2588)
                 at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2521)
                 at org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPage.java:2513)
                 at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2498)
                 at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
                 at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2493)
                 at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2478)
                 at org.eclipse.ui.ide.IDE.openEditor(IDE.java:388)
                 at org.eclipse.ui.ide.IDE.openEditor(IDE.java:350)
                 at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:275)
                 at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:139)
                 at org.eclipse.jdt.internal.ui.actions.OpenActionUtil.open(OpenActionUtil.java:49)
                 at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:190)
                 at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:174)
                 at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:267)
                 at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:243)
                 at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:306)
                 at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$4.open(PackageExplorerPart.java:651)
                 at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:817)
                 at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
                 at org.eclipse.core.runtime.Platform.run(Platform.java:843)
                 at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44)
                 at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149)
                 at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:815)
                 at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1069)
                 at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1168)
                 at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:249)
                 at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:243)
                 at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:283)
                 at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
                 at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
                 at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
                 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
                 at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
                 at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
                 at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
                 at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
                 at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
                 at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
                 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
                 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
                 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
                 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
                 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
                 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
                 at java.lang.reflect.Method.invoke(Unknown Source)
                 at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
                 at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
                 at org.eclipse.core.launcher.Main.run(Main.java:977)
                 at org.eclipse.core.launcher.Main.main(Main.java:952)
                !SUBENTRY 1 org.jbpm.gd.jpdl.ui.JpdlPlugin 4 0 2007-03-01 14:28:58.921
                !MESSAGE Error reading contents of file : gpd.xml.
                


                Do you need some files from me? or any hint what to do now?
                Thanks
                Bernd

                • 5. Re: jBPM jPDL GPD 3.1.0 alpha3 released
                  Koen Aers Master

                  Bernd,

                  Create a JIRA issue and attach the files that produce this phenomenon. Link the issue to this thread.

                  Thanks,
                  Koen

                  • 6. Re: jBPM jPDL GPD 3.1.0 alpha3 released
                    Johannes Huber Newbie

                    Hallo,

                    I tried to follow the example in JbpmGettingStarted (from Wiki) by creating a process with jPDL GPD 3.1.0 alpha3 release.
                    Everything works fine, except that I cannot define process variables for tasks.
                    In the property view of a TaskNode I can add a task, define its Assignment Type and set the Swimlane name, but I cannot see a possibility to define process variables.
                    Is this feature - definition of process variables for tasks - not implemented yet in this version or can this be done in a different manner?

                    Any help appreciated
                    Cheers,
                    Johannes

                    • 7. Re: jBPM jPDL GPD 3.1.0 alpha3 released
                      Koen Aers Master

                      Hi Johannes,

                      This was supposed to get implemented this week, but I have been busy with more urgent matters. It is anyhow the next thing on my task list.

                      Regards,
                      Koen

                      • 8. Re: jBPM jPDL GPD 3.1.0 alpha3 released
                        Ronald van Kuijk Master

                        more urgent matters... yeah right.... bollekes zeker :-)