12 Replies Latest reply on Jun 21, 2006 8:24 AM by Carmine Frasci

    Why process editor plug in doesn't work very well on eclipse

    Danilo Freitez Newbie

      Apparently the process editor plug in doesn't work very well on eclipse platform 3.1.1, because I have installed it and when I try to save a process the eclipse platform never finish this background task.

      So, I don't know if it is a bug of eclipse platform or process editor.

      Please let me know how to install it perfectly.

      Thanks you very much indeed in advance!

        • 1. Re: Why process editor plug in doesn't work very well on ecl
          Ronald van Kuijk Master

          Is there any info in the eclipse logging (in the .metadata subdir in the workspace dir)

          • 2. Re: Why process editor plug in doesn't work very well on ecl
            Danilo Freitez Newbie

            Hi Ronald,

            Thanks you very much for your short reply. So, there are 3 files on .metada dir named .lock, there is a file without name, and version, also there is a folder named .plugins.

            On file without name there is the following information:

            !SESSION 2005-12-29 11:12:33.362 -----------------------------------------------
            eclipse.buildId=I20050627-1435
            java.version=1.5.0_04
            java.vendor=Sun Microsystems Inc.
            BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_VE
            Command-line arguments: -os win32 -ws win32 -arch x86

            !ENTRY org.eclipse.core.resources 2 10035 2005-12-29 11:14:25.492
            !MESSAGE A workspace crash was detected. The previous session did not exit normally.

            !ENTRY org.eclipse.ui 4 4 2005-12-29 11:19:56.303
            !MESSAGE Unhandled event loop exception

            !ENTRY org.eclipse.ui 4 0 2005-12-29 11:19:56.303
            !MESSAGE org.eclipse.core.runtime.OperationCanceledException
            !STACK 0
            org.eclipse.core.runtime.OperationCanceledException
            at org.eclipse.core.internal.jobs.ThreadJob.joinRun(ThreadJob.java:158)
            at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:88)
            at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:190)
            at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:96)
            at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:1674)
            at org.eclipse.core.internal.resources.Folder.create(Folder.java:88)
            at org.eclipse.core.internal.resources.Folder.create(Folder.java:121)
            at org.jbpm.ui.wizard.NewProcessProjectWizard.createFolder(Unknown Source)
            at org.jbpm.ui.wizard.NewProcessProjectWizard.createOutputLocation(Unknown Source)
            at org.jbpm.ui.wizard.NewProcessProjectWizard.createJavaProject(Unknown Source)
            at org.jbpm.ui.wizard.NewProcessProjectWizard.performFinish(Unknown Source)
            at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:676)
            at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:349)
            at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:556)
            at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
            at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
            at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
            at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3080)
            at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2713)
            at org.eclipse.jface.window.Window.runEventLoop(Window.java:809)
            at org.eclipse.jface.window.Window.open(Window.java:787)
            at org.eclipse.ui.actions.NewProjectAction.run(NewProjectAction.java:114)
            at org.eclipse.jface.action.Action.runWithEvent(Action.java:996)
            at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
            at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
            at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
            at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
            at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
            at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3080)
            at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2713)
            at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
            at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
            at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
            at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
            at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
            at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
            at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
            at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
            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:334)
            at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
            at org.eclipse.core.launcher.Main.run(Main.java:973)
            at org.eclipse.core.launcher.Main.main(Main.java:948)
            !SESSION 2005-12-30 09:36:06.576 -----------------------------------------------
            eclipse.buildId=I20050627-1435
            java.version=1.5.0_04
            java.vendor=Sun Microsystems Inc.
            BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_VE
            Command-line arguments: -os win32 -ws win32 -arch x86

            !ENTRY org.eclipse.core.resources 2 10035 2005-12-30 09:37:53.810
            !MESSAGE A workspace crash was detected. The previous session did not exit normally.


            Regards!
            Danilo

            • 3. Re: Why process editor plug in doesn't work very well on ecl
              Ronald van Kuijk Master

              This is indeed the file, but since there is no info/error in there with regard to the jbpm GPD and no errors otherwise, it is impossible to help you on this level.

              You could try to increase the loglevel of the jBPM engine
              (log4j) and see if there is some error in there.

              If you are able to retrieve more infor on your problem, please post it here and we'd be happy to help you find the cause.

              • 4. Re: Why process editor plug in doesn't work very well on ecl
                Danilo Freitez Newbie

                Hi Ronald,

                I have tried to make myg process from the jpbm pug-in on eclipse platform, again. Now, eclipse has shown me a message on a dialog:
                "Building workspace (Waiting) (Blocks User Operation)
                Java-processdefinition.xml-Eclipse SDK
                "
                Regards!

                • 5. Re: Why process editor plug in doesn't work very well on ecl
                  Jerome BIABIANY Newbie

                  It is possible that eclipse try to validate your xml process definition and then try to load on internet the process definition "schema".
                  Your proxy or firewall may be blocking eclipse.

                  • 6. Re: Why process editor plug in doesn't work very well on ecl
                    Alejandro Guizar Master

                    I agree with phantomass. You can work around this problem easily, tough:
                    IIn Eclipse, go to Window->Preferences
                    Look for the Web and XML tree on your left and expand it
                    Click on the XML Catalog leaf
                    Add a catalog entry for the jPDL schema. In the URI field, browse for the schema document in JBPM_HOME/src/java.jbpm/org/jbpm/jpdl/xml/jpdl-3.0.xsd.
                    The key type is namespace name, and the key is the jPDL namespace http://jbpm.org/3/jpdl

                    • 7. Re: Why process editor plug in doesn't work very well on ecl
                      Koen Aers Master

                      I am currently working on a mechanism to add these entries in the XML catalog automatically and by default. So even behind a proxy server you will be able to make nice workflow diagrams without any pain ;-)

                      Regards,
                      Koen

                      • 8. Re: Why process editor plug in doesn't work very well on ecl
                        lucio piccoli Newbie

                        alex,

                        i have followed you directions to register the GPD schema with the eclipse XML catalogue however i am still getting the endless wait on saving a process. It is driving me crazy :-(

                        I am using
                        eclipse 3.1.1
                        GPD 3.0.5

                        below is the details of the catalogue entry

                        URI: file:D:\jbpm-starters-kit-3.0.2\jbpm\src\java.jbpm\org\jbpm\jpdl\xml\jpdl-3.0.xsd
                        Key Type: Namespace Name
                        Key: http://jbpm.org/3/jpdl


                        any help is appreciated

                        -lp

                        • 9. Re: Why process editor plug in doesn't work very well on ecl
                          Carmine Frasci Newbie

                          Hi

                          I'm experiencing the same problem but with eclipse 3.1.1 and jBPM plugin 3.0.9.2

                          Any help is appreciated.

                          regards!

                          • 10. Re: Why process editor plug in doesn't work very well on ecl
                            Ronald van Kuijk Master

                            I'm using 3.1.1 and 3.0.9.2 for several weeks now, without any problem. Can you define what your problem is

                            • 11. Re: Why process editor plug in doesn't work very well on ecl
                              Ronald van Kuijk Master

                              I'm using 3.1.1 and 3.0.9.2 for several weeks now, without any problem. Can you define what your problem is

                              • 12. Re: Why process editor plug in doesn't work very well on ecl
                                Carmine Frasci Newbie

                                When I design something and then save it, it takes a long time e.g. 2 min. until I can use my computer to work again. My whole system is locked up, the task manager shows a CPU usage of 100% and the process javaw.exe is the one that uses 100% of CPU!