[jBPM Users] - JBPM Graphical Process Designer 3.2 GA is incompatible with
by j2ee4cxw
I just did a fresh installation of MyEclipse Blue Edition (version 7.5), which is based on Eclipse 3.4.2 platform. Then I also installed Subclipse 1.6.x via the Help=>Software updates=>Add/Remove Software.
I have a jbpm-jpdl-3.2.GA download available. I unzipped it and tried to install the GPD via the Help=>Software updates=>Add/Remove Software by pointing to designer directory:
jbpm-jpdl-3.2.GA\designer
The installation went smoothly without any error. However, when I tried to an existing workflow definition, it throws following error.
I want to know any body has encountered this problem. Any suggestion or solution is greatly appreciated.
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.get(ArrayList.java:322)
at org.jbpm.ui.editor.DesignerContentProvider.addGraphicalInfo(Unknown Source)
at org.jbpm.ui.editor.DesignerContentProvider.addGraphicalInfo(Unknown Source)
at org.jbpm.ui.editor.DesignerContentProvider.addGraphicalInfo(Unknown Source)
at org.jbpm.ui.editor.DesignerContentProvider.addGraphicalInfo(Unknown Source)
at org.jbpm.ui.editor.DesignerGraphicalEditorPage.initInput(Unknown Source)
at org.jbpm.ui.editor.DesignerGraphicalEditorPage.init(Unknown Source)
at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:213)
at org.jbpm.ui.editor.DesignerEditor.addGraphPage(Unknown Source)
at org.jbpm.ui.editor.DesignerEditor.createPages(Unknown Source)
at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:310)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:428)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:594)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:306)
at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180)
at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270)
at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473)
at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256)
at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1209)
at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1608)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:499)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:485)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112)
at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63)
at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217)
at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207)
at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:779)
at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:678)
at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:639)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2817)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2729)
at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2721)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2673)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2668)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2652)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2643)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:646)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:605)
at org.eclipse.ui.actions.OpenFileAction.openFile(OpenFileAction.java:99)
at org.eclipse.ui.actions.OpenSystemEditorAction.run(OpenSystemEditorAction.java:99)
at org.eclipse.ui.views.navigator.OpenActionGroup.runDefaultAction(OpenActionGroup.java:125)
at org.eclipse.ui.views.navigator.MainActionGroup.runDefaultAction(MainActionGroup.java:329)
at org.eclipse.ui.views.navigator.ResourceNavigator.handleOpen(ResourceNavigator.java:716)
at org.eclipse.ui.views.navigator.ResourceNavigator$6.open(ResourceNavigator.java:443)
at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:820)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.runtime.Platform.run(Platform.java:880)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:818)
at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1079)
at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1183)
at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:263)
at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:257)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:297)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263052#4263052
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4263052
16 years, 5 months
[jBPM Users] - Re: JBPM4: How to find leaving transitions of an execution
by nilspreusker
Hi Sebastian,
anonymous wrote : Me: wouldn't it also be nice to be able to query the process instance for the process variables that will be required after a transition?
|
| Sebastian: Maybe you can explain your thoughts a bit more here.
My basic though is that the more details we can get about the process through the API at run-time, the closer we get to creating or generating a default user interface for processes.
If it was possible to retrieve information about the process variables that are required in the resulting task/state/activity node of a transition, one could think of a user interface that shows a default form when a transition is invoked (i.e. default task forms), based on the type and name of the variables. These could be customized by providing task forms along with the process deployment as it is shown in the task form example.
I suppose this is really turning more into a development forum discussion... Please let me know what you think!
Cheers, Nils
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262988#4262988
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262988
16 years, 5 months
[jBPM Users] - Re: JBPM4: How to find leaving transitions of an execution
by sebastian.s
"nilspreusker" wrote : Hi, I just voted:)
Great. :)
"nilspreusker" wrote :
| I think you are going in exactly the right direction. As I understand it (correct me if I'm wrong!), information about how the user can interact with the process instance in jBPM 4 is currently meant to be provided with task forms. A reference implementation exists for the GWT console. However, I totally agree with what Sebastian stated earlier:
|
| anonymous wrote : If you want the user to make this decision you need this information and since it is supplied by the process definition it should be accessible trough the API.
|
| For use cases where no user input - other than a decision - is required, this would provide a very nice way to create dynamic user interfaces without the need for a custom task form implementation.
|
I might even face similar use cases right now. My thoughts right now are pretty much related to dynamic user interfaces. I especially don't like the idea of creating task specific forms for simple things like decisions where just want to the user to decide between "yes" and "no", "A" and "B" etc.
"nilspreusker" wrote : And while we're at it, wouldn't it also be nice to be able to query the process instance for the process variables that will be required after a transition? ...but now I'm getting ahead of myself:)
|
I am not sure if this possible and if this would really make sense. Maybe you can explain your thoughts a bit more here.
"nilspreusker" wrote :
| Anyway, I'm glad to see this discussion here!
|
Yes, me too. This might turn out be a discussion for the developers' forum. I'd love to hear one of the dev's on this. To me at first sight it seems as if this is a "quite simple" API extension which shouldn't break anything.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262974#4262974
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262974
16 years, 5 months
[jBPM Users] - jbpm 4.1 - How to stop these Debug Messages in jboss
by makarandk502
Hi,
Jbpm 4.1 , Jboss 5.0.0 GA
When I see Jboss server log (server.log) from Jboss/server/default/log, I can see lot of following JobExecutor DEBUG messages. It seems that some process is running continuosly till we shutdown the jboss.
Server log size is becoming too much after some time.
Can anybody tell me how to stop printing DEBUG messages related to Jobexecutor ?
Your help is highly appreciated
|
| 18:46:33,942 DEBUG [DispatcherThread] DispatcherThread will wait for max 5000ms on org.jbpm.pvm.internal.jobexecutor.JobExecutor@7798cd
| 18:46:38,939 DEBUG [DispatcherThread] DispatcherThread woke up
| 18:46:38,949 DEBUG [AcquireJobsCmd] start querying first acquirable job...
| 18:46:38,949 DEBUG [AcquireJobsCmd] locking jobs []
| 18:46:38,959 DEBUG [GetNextDueDateCmd] getting next due date...
| 18:46:38,959 DEBUG [GetNextDueDateCmd] next due date is null
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262952#4262952
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262952
16 years, 5 months
[jBPM Users] - Re: JBPM4: How to find leaving transitions of an execution
by nilspreusker
Hi, I just voted:)
Regarding your doubts:
anonymous wrote : when the process arrives at a certaion point where a node has more than one outgoing transition, the user actually needs to make a choise which transition to take. So I need to display all possible transitions to the user.
|
| I'm still not sure if I'm running in the wrong direction, because this seems to obvious to me...
I think you are going in exactly the right direction. As I understand it (correct me if I'm wrong!), information about how the user can interact with the process instance in jBPM 4 is currently meant to be provided with task forms. A reference implementation exists for the GWT console. However, I totally agree with what Sebastian stated earlier:
anonymous wrote : If you want the user to make this decision you need this information and since it is supplied by the process definition it should be accessible trough the API.
For use cases where no user input - other than a decision - is required, this would provide a very nice way to create dynamic user interfaces without the need for a custom task form implementation.
And while we're at it, wouldn't it also be nice to be able to query the process instance for the process variables that will be required after a transition? ...but now I'm getting ahead of myself:)
Anyway, I'm glad to see this discussion here!
Cheers, Nils
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262950#4262950
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262950
16 years, 5 months
[jBPM Users] - Re: Logging mails in jBPM 4.0.CR1
by nilspreusker
Hi again,
I knew I would come across this again:) This time I'd like to implement a custom mail producer that uses a java class (in this particular case a spring bean) to generate attachments. The way I imagine it to work is that a custom producer first checks for the presence of a certain name (or a custom attachment type in addition to the existing ones; url, resource and file). If the name or type is present, the producer generates the custom attachment and then calls the default mail producer's addAttachment method (super.addAttachment) to take care of the rest. I think this is a pretty generic requirement, so I would like to contribute it as an example to the Developers Guide (if I actually succeed in implementing it).
What I know up to now is that I can extend org.jbpm.pvm.internal.email.impl.MailProducerImpl, as stated in the dev guide. I'm still not sure how I actually tell jBPM to use the custom producer. Maybe someone can point me at how to get the configuration right. The other challenge is to parse the inline mail template that defines the attachments, but looking at the source code of MailProducerImpl, extracting the relevant logic from there shouldn't be a big problem.
Thanks in advanced for your help!
Cheers, Nils
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262937#4262937
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262937
16 years, 5 months